Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1199642 - Content view promote of old version (or one without filters), results in old metadata
Summary: Content view promote of old version (or one without filters), results in old ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-06 20:59 UTC by sthirugn@redhat.com
Modified: 2017-02-23 20:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:56:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9904 0 None None None 2016-04-22 15:05:57 UTC
Red Hat Bugzilla 1218439 0 unspecified CLOSED Updating the activation key does not update metadata 2021-02-22 00:41:40 UTC

Internal Links: 1218439

Description sthirugn@redhat.com 2015-03-06 20:59:47 UTC 
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:
Comment 3 Justin Sherrill 2015-03-06 22:26:10 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.
Comment 4 Justin Sherrill 2015-03-25 21:23:45 UTC 
Created redmine issue http://projects.theforeman.org/issues/9904 from this bug
Comment 5 Bryan Kearney 2015-04-09 16:06:08 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/9904 has been closed
Comment 7 sthirugn@redhat.com 2015-04-29 17:14:28 UTC 
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.
Comment 9 sthirugn@redhat.com 2015-05-04 22:19:44 UTC 
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
Comment 10 Bryan Kearney 2015-08-11 13:30:08 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 11 Bryan Kearney 2015-08-12 13:56:13 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.