Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Note there is a workaround for this:
1) Create two activation keys Key "A" and Key "B", assign them both to the same lifecycle environment and content view
2) Assign no subscriptions to Key A
3) Assign a VDC subscription or some other subscription to Key B that provides content. This subscription does not even need to have any free entitlements available
4) Adjust the enabled content on Key B
5) Register a client with --activationkeys=A,B
The guest will use Key A to auto heal itself grabbing the guest subscription and then use Key B to grab the list of enabled repos.
Another way to workaround this is to add a sub to the activation key then enable/disable Product Content and then remove the sub from the activation key, this will still mean the options you set under Product Content will still be there you just can't change them unless you have a subscription attached to the activation key.
Comment 27Julio Entrena Perez
2016-11-01 16:14:38 UTC
Workaround in comment 25 seems to work, thank you Sean!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:0336