Bug 251275

Summary: erroneous message "cannot access installation media" from yast2 Software Management
Product: [openSUSE] openSUSE 10.3 Reporter: Casual J. Programmer <casualprogrammer>
Component: libzyppAssignee: Jan Kupec <jkupec>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P3 - Medium CC: aj
Version: Alpha 3   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 10.3   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: YasT2 logs
screenshot of yast, firefox and error message
screenshot of yast, firefox and error message
Screenshot of message box
YaST2 logs
yast2logs
yast2logs
Most recent yast2 logs
complete y2log
yast2logs from todays update

Description Casual J. Programmer 2007-03-05 15:04:57 UTC
In openSUSE 10.3 alpha 2, often the message "cannot access installation media" is issued erroneously, i.e.

searching for spicctrl offers spicctrl-1.8-42.i586 from source http://download.opensuse.org/distribution/SL-OSS-factory/inst-source ,
when selecting it and activating "accept" a message-box appears stating:

"cannot access installation media .... check that the server is available", when checking "Show details", it states:

"Media source http://download.opensuse.org/distribution/SL-OSS-factory/inst-source does not contain the desired media"

On visiting the source with a webbrowser, spicctrl-1.8-42.i586.rpm is listed and can be downloaded and installed.

This happens with a quite a few packages recently
Comment 1 Casual J. Programmer 2007-03-05 15:10:36 UTC
Created attachment 122343 [details]
YasT2 logs
Comment 2 Ladislav Slezák 2007-03-29 12:30:32 UTC
That's strange, I couldn't reproduce the problem. I could install spicctrl-1.8-44.i586.rpm in Alpha2plus from the FACTORY source.

I think it might have been caused by an inconsistency in the metadata on the server. If it still happen then reopen.
Comment 3 Casual J. Programmer 2007-03-30 07:48:13 UTC
Actually happens just now ( 200703300945 ), see attached screenshots.
Comment 4 Casual J. Programmer 2007-03-30 07:49:46 UTC
Created attachment 127631 [details]
screenshot of yast, firefox and error message
Comment 5 Casual J. Programmer 2007-03-30 07:50:08 UTC
Created attachment 127632 [details]
screenshot of yast, firefox and error message
Comment 6 Casual J. Programmer 2007-03-30 07:58:35 UTC
This may well be a problem of the mirror server redirection and its management ( I noticed, there is a lot of redirection going on ), but this should be fixed then, and YaST should be able to handle it properly as well.
Comment 7 Casual J. Programmer 2007-04-15 10:53:28 UTC
I experienced this today a lot, after clicking "OK" several times ( 5 to 20 ) it recovers and does download. 

As I mentioned in Comment #6, my impression is, that there is a whole lot of sources "hidden" behind the registered source, and it seems that not all of them are accessible properly or updated properly. 

This is really a nuisance and makes automated updates almost impossible. There should be some means to make YaST retry several sources automatically. ( Maybe there is, and I just haven't found out? )


Comment 8 Casual J. Programmer 2007-04-15 10:54:34 UTC
Created attachment 131211 [details]
Screenshot of message box
Comment 9 Casual J. Programmer 2007-04-15 11:07:08 UTC
Created attachment 131212 [details]
YaST2 logs
Comment 10 Casual J. Programmer 2007-04-20 14:30:56 UTC
Created attachment 132877 [details]
yast2logs
Comment 11 Casual J. Programmer 2007-04-20 14:41:39 UTC
Created attachment 132879 [details]
yast2logs
Comment 12 Casual J. Programmer 2007-05-01 09:20:33 UTC
Created attachment 136752 [details]
Most recent yast2 logs
Comment 13 Casual J. Programmer 2007-05-01 09:28:11 UTC
Not sure why this should be so, on most updates I cant leave the PC alone as pressing OK is required VERY frequently. Sometimes I need to run yast2 inst_source and read in all sources again to get going,
Comment 14 Ladislav Slezák 2007-05-02 12:39:09 UTC
I could reproduce the problem when adding source 
http://download.opensuse.org/distribution/SL-OSS-factory-debug/inst-source-debug

2007-05-02 14:32:31 <0> cyclops(4721) [zypp] PathInfo.cc(_Log_Result):296 rename /var/adm/mount/AP_0x00000047/media.1/media.new.zypp.eHZbBF -> /var/adm/mount/AP_0x00000047/media.1/media
2007-05-02 14:32:31 <0> cyclops(4721) [zypp] MediaCurl.cc(doGetFileCopy):1314 done: /var/adm/mount/AP_0x00000047/media.1/media{- 0644 0/0 size 42}
2007-05-02 14:32:31 <0> cyclops(4721) [zypp] MediaHandler.cc(provideFile):1008 provideFile(/media.1/media)
2007-05-02 14:32:31 <0> cyclops(4721) [zypp] MediaManager.cc(checkDesired):106 checkDesired(11): not desired (report by N4zypp6source10SourceImpl8VerifierE)
2007-05-02 14:32:31 <5> cyclops(4721) [zypp] Exception.cc(log):94 /local/lslezak/ZYPP-opensuse.org/libzypp/zypp/media/MediaManager.cc(checkDesired):110 THROW:    /local/lslezak/ZYPP-opensuse.org/libzypp/zypp/media/MediaManager.cc(checkDesired):110: Media source http://download.opensuse.org/distribution/SL-OSS-factory-debug/inst-source-debug/ does not contain the desired media

Jano, any idea?
Comment 15 Jan Kupec 2007-05-02 13:33:28 UTC
basically SourceImpl::Verifier::isDesiredMedia() returned false ((vendor == _media_vendor && id == _media_id) was false). In other words, vendor and media id strings read while setting media verifier differ from the ones read during this particular operation.

I have no clue how that could happen, tough.

I will need the rest of the logs.

BTW: zypper add http://download.opensuse.org/distribution/SL-OSS-factory-debug/inst-source-debug works for me.

Which version of zypp are we talking about? The one from Aplha3?
Comment 16 Ladislav Slezák 2007-05-02 13:46:36 UTC
Created attachment 137000 [details]
complete y2log

This is the complete y2log when the error message is displayed.

I have libzypp from SVN repo, installed about one week ago.
Comment 17 Casual J. Programmer 2007-05-02 21:26:49 UTC
Created attachment 137113 [details]
yast2logs from todays update

libzypp is now 3.2.0-5, not sure whether it was updated, if so version was the one before when updating.
Comment 18 Ladislav Slezák 2007-05-09 12:29:46 UTC
*** Bug 271323 has been marked as a duplicate of this bug. ***
Comment 19 Jan Kupec 2007-05-10 18:09:13 UTC
I was able to reproduce the bug, and after few hours a came to realize that the problem lies indeed outside of zypp.

Each time you click on 'media' file at http://download.opensuse.org/distribution/SL-OSS-factory-debug/inst-source-debug/media.1/
you get redirected to some mirror.

Sometimes you get:
SUSE Linux Products GmbH
20061202045441
1

sometimes you get:
SUSE Linux Products GmbH
20070509141425
1

and sometimes you get error 404!

Comment 20 Jan Kupec 2007-05-10 18:49:56 UTC
I was able to reproduce the bug, and after few hours a came to realize that the problem lies indeed outside of zypp.

Each time you click on 'media' file at http://download.opensuse.org/distribution/SL-OSS-factory-debug/inst-source-debug/media.1/
you get redirected to some mirror.

Sometimes you get:
SUSE Linux Products GmbH
20061202045441
1

sometimes you get:
SUSE Linux Products GmbH
20070509141425
1

and sometimes you get error 404!

This is why zypp considers the media not desired (see comment #15).

So it depends on whether mirror are synchronized.

*** This bug has been marked as a duplicate of bug 239625 ***

*** This bug has been marked as a duplicate of bug 239625 ***
Comment 21 Jan Kupec 2007-05-10 18:57:31 UTC
i found a better duplicate
Comment 22 Jan Kupec 2007-05-10 18:57:53 UTC

*** This bug has been marked as a duplicate of bug 238095 ***