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 1218439 - Updating the activation key does not update metadata
Summary: Updating the activation key does not update metadata
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: sthirugn@redhat.com
URL:
Whiteboard:
Depends On: 1218646
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-04 22:17 UTC by sthirugn@redhat.com
Modified: 2017-02-23 20:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1218646 (view as bug list)
Environment:
Last Closed: 2015-09-25 14:15:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1166304 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1199642 0 unspecified CLOSED Content view promote of old version (or one without filters), results in old metadata 2021-02-22 00:41:40 UTC

Internal Links: 1166304 1199642

Description sthirugn@redhat.com 2015-05-04 22:17:55 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
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.

Actual results:
Step 8 failed

Expected results:
Step 8 should pass

Additional info:
This is found while verifying bug https://bugzilla.redhat.com/show_bug.cgi?id=1199642#c7

Comment 2 Adrian Likins 2015-08-05 16:18:55 UTC
> 8. Attempt to install any package or errata in ch2 and notice that it fails.

Needinfo, need a copy of any error messages.

redhat.repo should be updated based on the new entitlement certificates,
so verify that new redhat.repo is pointing to the proper content.

What does 'apply some filters' mean? Does that change the repo metadata?

Is this metadata expire related?

Comment 3 sthirugn@redhat.com 2015-09-15 19:57:15 UTC
Verified in Sat 6.1.2 build and it works fine now.

Comment 4 Brad Buckingham 2015-09-25 14:15:51 UTC
Moving to CLOSED:CURRENTRELEASE since it was verified on 6.1.2.


Note You need to log in before you can comment on or make changes to this bug.