Description of problem: We have got Sat5.7 with HighAvailability or LoadBalancer channel, but we do not see this channels in kickstart profile as repository. Version-Release number of selected component (if applicable): Satellite-5.7.0-RHEL6-re20141001.0 How reproducible: 100% Steps to Reproduce: 1. Sync rhel-x86_64-server-6 and rhel-x86_64-server-ha-6 channels 2. Open some kickstart profile with RHEL6 > "Kickstart Details" > "Operating System" 3. We do not see repository
Well, these commits fix a regression against sat5.6, so the repos will be displayed on WebUI (for rhel6): spacewalk.git: 8e00387aad54df1a1860fa66f69433f0450c82ca 825f73c8579366f487ff997b5ff416ce1739efd4 Note the repository paths are different for RHEL7, so these commits do not discover the RHEL7 repositories.
I have filed new bug bz1153994 about the synchronization of RHEL7 channels. The bug 1153994 is blocker for this bug.
All right, in that case I move this bug to MODIFIED.
VERIFIED on Satellite-5.7.0-RHEL6-re20141017.0 (spacewalk-java-2.3.8-44.el6sat) This verification is only for the RHEL6 channel, for RHEL7 is a clone here bz1154548. Reproducer: 1. Sync RHEL6 kickstart > satellite-sync -c rhel-x86_64-server-6 --no-errata --no-packages --no-rpms 2. Open some kickstart profile with RHEL6 > "Kickstart Details" > "Operating System" 3. we can see: Repositories: * HighAvailability * LoadBalancer * ResilientStorage * ScalableFileSystem Kickstart repositories of child channels are downloaded together with the base kickstart.
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is being moved to a Closed Current Release state. The Satellite 5.7 GA Errata: - https://rhn.redhat.com/errata/RHSA-2015-0033.html Satellite 5.7 Release Notes: - https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html Satellite Customer Portal Blog announcement for release: - https://access.redhat.com/blogs/1169563/posts/1315743 Cliff NOTE: This bug has not been re-verified (moved to RELEASE_PENDING) prior to release. We assume that the bug has indeed been fixed and not regressed since we initially verified it. Please re-open in the future if needed.