DescriptionPreetesh Sharma
2016-06-08 15:20:59 UTC
1. Proposed title of this feature request
Ability to use subscription associated to hypervisor when adding a server with activation key
2. What is the nature and description of the request?
Currently in order to use properly subscription manager with datacenter licences, the activation key must be empty from subscription or we need to use --auto-attach.
Otherwise the subscription in the activation key will be consumed, even if the hypervisor have a valid licence.
3. Why do you need this? (List the business requirements here)
1) We need to use the same activation key for virtual and physical server
2) We need to use activation key because it will trigger functionalities on the server (repo, ...)
5. How would you like to achieve this? (List the functional requirements here)
We would like to have a "prefer hypervisor licence" flag on the activation key, for each attached subscription.
If one host is virtual, and the flag is on, the guest will take the licence from the hypervisor.
Otherwise the current method will be used, and the subscription will be consumed.
6. For each functional requirement listed, specify how Red Hat and you can test to confirm the requirement is successfully implemented.
1) create one activation key
2) attach subscriptions with "prefer hypervisor licence" flag on
3) attach subscription on one hypervisor
4) on one new host running on the selected hypervisor, run subscription-manager with the activation key created
we expect to see no subscription consumed on the activation key.
7. Does you have any specific timeline dependencies and which release would they like to target (i.e. RHEL6, RHEL7)?
We need it by the end of the year 2016, when we will have a massive renewal
8. List any affected packages or components.
Satellite 6.2
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