Bug 1172853

Summary:	If a VM becomes unregistered or subscriptions detach it loses subscription to additional repositories
Product:	Red Hat Enterprise Linux 6	Reporter:	Sal Castiglione <castigliones>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED CURRENTRELEASE	QA Contact:	John Sefler <jsefler>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	bcourt, castigliones, dgoodwin
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-09 17:16:25 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:
Bug Blocks:	1209535

Description Sal Castiglione 2014-12-10 22:28:46 UTC

Description of problem:

I've seen several systems have their subscription become unattached and then error  when attempting to update packages via 'yum update' that were previously installed as part of the rhel-6-server-supplementary-rpms or rhel-6-server-optional-rpms.

The subscriptions became unattached when the virt-who server was unavailable for a period a few times - and then automatically re-attached their licenses (auto-attach option is enabled)

I can re-create this behavior by removing its subscriptions manually - then re-attaching them.  Listing the installed repositories shows it as disabled.  It needs to then be re-enabled using either:
subscription-manager repos --enable=rhel-6-server-supplementary-rpms
or 
yum-config-manager --enable rhel-6-server-supplementary-rpms

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


How reproducible:

Always

Steps to Reproduce:
1. Add rhel-6-server-supplementary-rpms (or another Red Hat Repo requiring a subscription)
2. Install an older or obsolete version of a package from the repo
3. Let the system's subscription lapse or manually unattached (subscription-manager remove --all)
4. Let the system automatically re-attach (auto-attach) or manually re-attach (subscription-manager attach --auto)
5. Try to run a 'yum update' to see it error and/or do a 'yum repolist all' to see it as disabled.


Actual results:


Expected results:


Additional info:

Comment 2 Devan Goodwin 2015-04-07 15:50:31 UTC

Should be working if using subscription-manager repos command in latest versions, this is applied as an override on the system and will persist across entitlement events provided you do not re-register.oss re-entitlement.

yum-config-manager changes will get clobbered if the repo goes away entirely in the meantime. (nothing we can do about this)

Comment 3 Sal Castiglione 2015-04-20 15:45:28 UTC

Great, thanks.