Bug 1199642
Summary: | Content view promote of old version (or one without filters), results in old metadata | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | sthirugn <sthirugn> |
Component: | Container Management | Assignee: | Justin Sherrill <jsherril> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | sthirugn <sthirugn> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1.0 | CC: | bbuckingham, bkearney, jsherril, mmccune |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://projects.theforeman.org/issues/9904 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-12 13:56:13 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
sthirugn@redhat.com
2015-03-06 20:59:47 UTC
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. |