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.
DescriptionChristophe Augello
2015-01-07 10:00:55 UTC
Description of problem:
Only one subscription from Virtual Datacenter can be attached for activation key
Version-Release number of selected component (if applicable):
6.0.6
How to reproduce:
Satellite 6
Virt-who
Virtual datacenter subscription
A Virtualization environment with multiple hypervisors with a VDC subscription attached to them.
Steps to Reproduce:
1. Create a activation key
2. Attach a virtual datacenter subscription
Actual results:
Only one VDC subscription can be attached to activationkey.
When provision from a VM from satellite, if guest is on hypervisor registration succeed else not.
Expected results:
Add all available VDC subscription to be able to use the activationkey among all hypervisors that are linked to the attached subscriptions.
Additional info:
Current workaround is to not use the activationkey and add in kickstart script :
# subscription-manager attach --auto
The ability to add multiple hypervisor subscriptions to an a single activation key will be available in the next release (6.1).
*** This bug has been marked as a duplicate of bug 1161642 ***