Red Hat Bugzilla – Bug 1161642
As a user, I wish to add guest subscriptions from different hypervisors to a single activation key
Last modified: 2017-02-23 15:49:36 EST
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.
Merged to candlepin
*** Bug 1179670 has been marked as a duplicate of this bug. ***
Verified. Version Tested: Satellite-6.1.0-RHEL-6-20150210.0 Satellite-6.1.0-RHEL-7-20150210.0
*** Bug 1209481 has been marked as a duplicate of this bug. ***
(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.
Yes I still need to create one activationkey for each contentview and then for echa Environment......
But this BZ is to allow multiple hypervisors on a single key. If that capability is available, please conclude this issue and begin a new one.
This is something that we need as well (multiple hypervisors in a single key). We have +100 hypervisors in play..
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
This bug is slated to be released with Satellite 6.1.
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