Bug 439068

Summary: software management: contradictory error message "repository not cached"
Product: [openSUSE] openSUSE 11.1 Reporter: macias - <bluedzins>
Component: YaST2Assignee: Ladislav Slezák <lslezak>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P2 - High CC: jim.petersen
Version: Beta 4   
Target Milestone: ---   
Hardware: i586   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 439069    
Attachments: y2logs.tgz
y2logs.tgz

Description macias - 2008-10-26 17:18:12 UTC
I am about to run SM for the first time in OS11.1B3 and I see error dialog:

There was an error in repository initialization
'repo-oss': Repository not cached.

Of course it is not cached, because it is _initialization_. The first run. You cannot expect anything is cached before first run, can't you?
Comment 1 Michal Seben 2008-10-27 10:25:02 UTC
Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!
Comment 2 macias - 2008-10-27 12:32:32 UTC
Created attachment 248087 [details]
y2logs.tgz
Comment 3 Stanislav Visnovsky 2008-10-27 13:46:34 UTC

*** This bug has been marked as a duplicate of bug 437936 ***
Comment 4 macias - 2008-11-05 13:28:26 UTC
Reopening as requested.
Comment 5 macias - 2008-11-05 13:29:31 UTC
And changing version.
Comment 6 Jan Kupec 2008-11-05 15:50:01 UTC
> Reopening as requested.
requested where, why, or by whom?

The log says you don't have network connection at the point of starting the SM. If that's so, you can't cache the repository.

2008-10-26 14:20:15 <2> linux(3601) [Pkg] Source_Resolvables.cc(LoadResolvablesFrom):96 No network connection, skipping autorefresh of remote repository repo-oss (http://download.opensuse.org/distribution/11.1/repo/oss/)
2008-10-26 14:20:15 <5> linux(3601) [zypp] Exception.cc(log):119 RepoManager.cc(loadFromCache):1172 THROW:    RepoManager.cc(loadFromCache):1172
: Repository not Cached
2008-10-26 14:20:15 <3> linux(3601) [Pkg] Source_Resolvables.cc(LoadResolvablesFrom):129 Resolvables from 'repo-oss' havn't been loaded: Repository not Cached


So, as Lada suggests in bug #437936 c#7, this is probably a duplicate of bug #435970. Is that so (do yast2-pkg-bindings-2.17.20 fix the problem) or is there a real problem with your network connection?
Comment 7 macias - 2008-11-05 16:01:33 UTC
By Ladislav, see:
https://bugzilla.novell.com/show_bug.cgi?id=435970#c11

> The log says you don't have network connection at the point of starting the
> SM.

I have network connection, no problem.

> Is that so (do yast2-pkg-bindings-2.17.20 fix the problem) 

Nope, I have even newer version.

Besides, please read the error carefully. It says it was an error during initialization. And the error was the cache was not found.

And it cannot be -- you cannot initialize something before initialization. Cache can be created _after_ initialization, how cache can be created before fetching data for the first time? The logic is faulty here (too?).
Comment 8 Jan Kupec 2008-11-06 14:49:28 UTC
Thanx, turning over to Lada, then.
Comment 9 Ladislav Slezák 2008-11-06 14:55:47 UTC
Please, attach y2log from Beta4.
Comment 10 macias - 2008-11-06 15:06:25 UTC
Created attachment 250338 [details]
y2logs.tgz
Comment 11 Ladislav Slezák 2008-11-06 15:50:24 UTC
Um, I have found it:
2008-11-04 12:23:07 <1> linux(20495) [Pkg] Network.cc(NetworkDetected):51 Network is running: yes
2008-11-04 12:23:07 <1> linux(20495) [Pkg] Network.cc(NetworkDetected):57 Network (IPv6) is running: no
2008-11-04 12:23:07 <2> linux(20495) [Pkg] Source_Resolvables.cc(LoadResolvablesFrom):96 No network connection, skipping autorefresh of remote repository openSUSE-11.1-Updates (http://download.opensuse.org/update/11.1/)
Comment 12 Ladislav Slezák 2008-11-07 10:24:07 UTC
Fixed in yast2-pkg-bindings-2.17.23 - there is only IPv4 test now.
Comment 13 Jan Kupec 2008-11-10 14:18:57 UTC
*** Bug 438498 has been marked as a duplicate of this bug. ***
Comment 14 Jan Kupec 2008-11-15 17:29:12 UTC
*** Bug 444869 has been marked as a duplicate of this bug. ***