RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1172853 - If a VM becomes unregistered or subscriptions detach it loses subscription to additional repositories
Summary: If a VM becomes unregistered or subscriptions detach it loses subscription to...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel68
TreeView+ depends on / blocked
 
Reported: 2014-12-10 22:28 UTC by Sal Castiglione
Modified: 2015-10-09 17:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-09 17:16:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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