Hello list,
after upgrading to spacewalk 1.8 the problem disappeared... I can now refresh the repository in question: uwe01:/var/log/zypp # zypper ref sles11-sp2 Retrieving repository 'sles11-sp2' metadata [done] Building repository 'sles11-sp2' cache [done] Specified repositories have been refreshed. Greetings, Sabine Von: [email protected] [mailto:[email protected]] Im Auftrag von [email protected] Gesendet: Dienstag, 6. November 2012 10:17 An: [email protected] Betreff: [Spacewalk-list] SLES11 SP2: Problem with SLES11 SP2 Repository -repomd.xml not found Hello list, since I haven't found a possibility to install spacewalk on SLES11 SP1 I have updated to SP2. I've registered 2 server running sles11 sp2 to spacewalk base channel sles11_sp2 (including sles11_sdk_sp2, sles11_sdk_sp2_updates, sles11_sp2_updates as child-channels which are working fine), but I've still got a problem with the base channel. I can repo-sync the base channel on the spacewalk server without any problem: [root@spacewalk logs]# spacewalk-repo-sync --channel sles11_sp2 Repo URL: https://user:[email protected]/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/ Packages in repo: 739 No new packages to sync. Repo https://user:[email protected]/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/ has 0 errata. Sync completed. Total time: 0:00:36 But, when I try to refresh my repository on the Client, I do get the following error: uwe01:/var/log/zypp # zypper ref -f sles11-sp2 Forcing raw metadata refresh Retrieving repository 'sles11-sp2' metadata [\] File '/repodata/repomd.xml' not found on medium 'http://spacewalk.der.de/XMLRPC/GET-REQ/sles11_sp2?head_requests=no' Abort, retry, ignore? [a/r/i/?] (a): a Retrieving repository 'sles11-sp2' metadata [error] Repository 'sles11-sp2' is invalid. [|] Valid metadata not found at specified URL(s) Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'sles11-sp2' because of the above error. Could not refresh the repositories because of errors. Btw.: on the Client the repos look like this # zypper lr # | | Name | Enabled | Refresh ---+----------------------------------------------------+--------------- ---------------------+-----------------+-------- 15 | spacewalk:sles11_sdk_sp2 | sles11_sdk_sp2 | Yes | Yes 16 | spacewalk:sles11_sdk_sp2_updates | sles11_sdk_sp2_updates | Yes | Yes 17 | spacewalk:sles11_sp2 | sles11-sp2 | Yes | Yes 18 | spacewalk:sles11_sp2_updates | sles11_sp2_updates | Yes | Yes Refreshing of the Child Channels on client side is also working fine... # zypper ref sles11_sp2_updates Repository 'sles11_sp2_updates' is up to date. Specified repositories have been refreshed. Of course I get the same error, when I try to install updates from SLES11-SP1 Base Channels via Spacewalk GUI (updates from child channels are also working fine): Refreshing service 'spacewalk'. File '/repodata/repomd.xml' not found on medium 'http://spacewalk.der.de/XMLRPC/GET-REQ/sles11_sp2?head_requests=no' Repository 'sles11-sp2' is invalid. [|] Valid metadata not found at specified URL(s) Please check if the URIs defined for this repository are pointing to a valid repository. Disabling repository 'sles11-sp2' because of the above error. Loading repository data... Reading installed packages... Package 'yast2-installation-2.17.99-0.5.22' not found. I don't think that the Uri is invalid, because I can successfully sync the repo on the server, as shown above. Now, when I look at the basic channel details from the spacewalk GUI I've noticed the following for the channel sles11_sp2: Last Repo Build: (none) Repo Cache Status: In Progress When compared with other channels, e.g. the Child Channel "sles11_sdk_sp2" it says: Last Repo Build: 2012-11-02 13:46:43 CET Repo Cache Status: Completed Can anybody help, please? Greetings from Germany, Sabine
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
