Description of problem: spacewalk not sycning the correct repodata.. at least not the one specified in the repository path. I'm never see grouplist data Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What repo are you syncing? Is there comps.xml in the remote repo?
Presently on the spacewalk 1.7 I have CentOS 5.9 base update EPEL5 spacewalk1.7-client-rhel5 CentOS 6.3 base update EPEL6 spacewalk1.7-client-rhel6 CentOS 6.4 base updates Epel6 spacewalk1.7-client-rhel6 On my newly created spacewalk 1.9 server I have CentOS 5.9 base update EPEL5 spacewalk1.9-client-rhel5 CentOS 6.3 base update EPEL6 spacewalk1.9-client-rhel6 CentOS 6.4 base updates Epel6 spacewalk1.9-client-rhel6 Description of problem: spacewalk not sycning the correct repodata.. at least not the one specified in the repository path. I'm never see grouplist data Version-Release number of selected component (if applicable):1.9 or 1.47 How reproducible: Bug 585338 I'm running spacewalk not RHN so I don't know where the make the changes manually as listed in this bug.. I roadmap stated that 1.9 have this feature. Steps to Reproduce: 1. create channel and repository in spacewalk.. sync the channel repo.. Actual results: channel uploads all the package data. view /var/cache/rhn/repodata/<channel_id> is had its own repomd.xml filelist.xml.gz other.xml.gz and primary.xml.gz these files don't match the repodata in the channel repository that is pulls the packages from i.e. http://spacewalk/yum/centOS6/x86_64/Packages/repodata Expected results: I'd expect the repodata to get pulled from the channel that houses the Packages.
What is the URL of the *remote* yum repository that your are syncing with spacewalk-repo-sync? Please give us *one* example.
This is the name of my remote repository http://spacewalk/yum/centOS6/x86_64/Packages/ the repodata is located inside the Packages directory and for good measure I removed it from http://spacewalk/yum/centOS6/x86_64/ and copied the newly created repodata dir here also.. x86_64 = OS directory but on spacewalk 1.7 the group data never gets created it is ignore It looks like it takes the repodata from the kickstart channel data instead of from the Software channel I created. I was having this issue on 1.9 until I created a seperate channel for the Kickstart CentOS 6.4 then removed and created a new CentOS 6.4 OS channel. I didn't try using the same name as before.. for the Base. With that the group data was brougth into the SW Channel without issue. It failed when I tried to empty the channel and re-sync.. on Spacewalk 1.7 after moving the Kickstart Channel to a seperate location and not associating it with any managaged repository. I tried to empty the channel, re-create the channel, and creating a fresh channel with a different name all failed to gather group data.
We'll start by taking Spacewalk 1.7 out of the picture -- the code to sync the comps information is only available in Spacewalk 1.8+, as noted at https://fedorahosted.org/spacewalk/wiki/ReleaseNotes18 The http://spacewalk/yum/centOS6/x86_64/Packages/ is not a remote URL -- it's URL local to your Spacewalk (judging by the name) and we have no idea how it got there and what the repodata content is. But you seem to have made it work with Spacewalk 1.9. Closing as NOTABUG.
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.