Description of problem: Unable to install a package or errata in content-host after a new publish/promote of a content view Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-6-20150303.0 How reproducible: Always Steps to Reproduce: 1. Create a content view cv1 - apply some filters (to remove all packages and errata), publish, promote 2. create an activation key ak1 and attach the content view from step1 3. Register/Subscribe a content host using ak1 4. Perform the following in content host to make sure it looks good: yum clean all && yum repolist 5. Now remove few filters in the content view cv1, publish, promote to include new packages, errata that were not present in the publish in Step 1 6. Go to Hosts -> Content Hosts -> Select the content host from Step 3 -> Attempt to install a new package / errata which is introduced with the new publish from Step 5 and not present in Step 1 Actual results: - The task is completed in Satellite and showed GREEN - But the errata is not actually installed in the content host. The pulp error from the content host is attached Expected results: Additional info:
It appears the cause of this is the fact that we are using the puppet clone distributor. we should change the behaviour to only use that distributor if the destination repo does not exist, or else modify the clone distributor to rewrite the repomd.xml file.
Created redmine issue http://projects.theforeman.org/issues/9904 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/9904 has been closed
Also this scenario failed. QE is requested to verify the scenario while retesting this bug: 1. Create a content view cv1 - apply some filters (to remove some errata), publish, promote 2. create an activation key ak1 and attach the content view from step1 3. Register/Subscribe a content host ch1 using ak1 4. Perform the following in content host to make sure it looks good: yum clean all && yum repolist 5. Create a new content cv2 and use the same repo as in Step 1, but dont use any filters - just publish and promote 6. Create an other activation key ak2 with cv2 7. Now unregister ch1 and re-register it with ak2 8. Attempt to install any package or errata in ch2 and notice that it fails. Workaround: yum clean all in ch1 and attempt to install any package or errata - it works fine then.
Verified. Version Tested: Satellite-6.1.0-RHEL-7-20150429.2 Note that the steps mentioned in description now works fine. But steps in Comment #7 failed which is logged as a separate bug https://bugzilla.redhat.com/show_bug.cgi?id=1218439
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.