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.
DescriptionAlexander von Gluck IV
2015-04-07 13:01:23 UTC
Description of problem:
Satellite Server 6 doesn't allow you to attach more than one virtual datacenter subscription to an activation key.
Version-Release number of selected component (if applicable):
6.0.8
How reproducible:
easily.
Steps to Reproduce:
1. Have more than one ESX virtual datacenter host (unlimited guests) properly configured with virt-who
2. Create a new activation key
3. Attach all "unlimited" guest subscripttions to it.
4. Only one unlimited subscription gets added to the key.
5. Additional unlimited subscription additions fail.
Actual results:
Only one activation key per licensed ESX host.
You have to match activation keys to vm's on certain ESX hosts.
Unsustainable in large environments.
Comment 1RHEL Program Management
2015-04-07 13:13:35 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.