Bug 1218439

Summary: Updating the activation key does not update metadata
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: Activation KeysAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: sthirugn <sthirugn>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: alikins, bbuckingham, bkearney, sthirugn
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1218646 (view as bug list) Environment:
Last Closed: 2015-09-25 14:15:51 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:
Bug Depends On: 1218646    
Bug Blocks:    

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.