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.
The new activation key code that allows the "auto-attach" option should allow adding generated "unlimited" guest subscriptions to an activation key, even if from different hypervisors.
The use case is a single activation key that may be used by any guest, no matter which hypervisor it is provisioned on.
(In reply to Tom McKay from comment #0)
> The new activation key code that allows the "auto-attach" option should
> allow adding generated "unlimited" guest subscriptions to an activation key,
> even if from different hypervisors.
>
> The use case is a single activation key that may be used by any guest, no
> matter which hypervisor it is provisioned on.
But I want use activationkeys so that I can attach the VM to a specific Lifecycle Environment.
Folks in GSS and anyone cc'd or commenting. This RFE is approved and already verified for the Satellite 6.1 release. Consider this RFE DONE.
If you have new requests for new features and enhancements to the behaviour of Activation Keys - please open NEW RFE's and attach the customer cases there. Myself, nor others will act on comments in this bug asking for more stuff. They need to be broken into their own RFEs and triaged and approved on a case-by-case basis. The Satellite 6.1 release is feature frozen, so RFEs will be considered for future releases.
The general process for submitting RFEs can be found here:
https://mojo.redhat.com/docs/DOC-110680#jive_content_id_Red_Hat_Satellite__Proxy
If you have questions on the GSS RFE process, please work with your local GSS supervisor or Xixi.
Regards,
Cliff
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-2015:1592