Feature #16574
open
Allow activation keys to enable product repos regardless of whether there is a subscription attached or not
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1265125
1. Proposed title of this feature request
Allow activation keys to enable product repositories regardless of whether there is a subscription attached or not.
3. What is the nature and description of the request?
- Create an activation key without any subscriptions attached but auto-attach set to true.
- Pick from the comprehensive list of available repos and set enable/disable on some.
- Client runs subscription-manager register with the activation key which results in
A) client gets a temporary subscription if virt-who has not run, or
B) client gets a guest subscription if virt-who has alrady run
- Repos are enabled as expected after registration without the need for a second call to subscription-manager
4. Why does the customer need this? (List the business requirements
here)
For example I have a customer who has an activation key that has multiple derived VDC unlimited subscriptions
attached to it and wants the machines to activate particular product content based on this AK.
When this activation key is used in the provisioning stage while the virt-who mapping has not completed the subscriptions will fail and no content is available for this VM.
If the customer where to use the 24 hours grace period with the temporary subscription he would need to register the VM once more afterwards to have the correct subscriptions and repos attached to it as the temporary subscription was not meant to be used with an AK.
5. How would the customer like to achieve this? (List the functional
requirements here)
- Create an activation key without any subscriptions attached but auto-attach set to true.
- Pick from the comprehensive list of available repos and set enable/disable on some.
- Client runs subscription-manager register with the activation key which results in
A) client gets a temporary subscription if virt-who has not run, or
B) client gets a guest subscription if virt-who has alrady run
6. For each functional requirement listed in question 5, specify how Red
Hat and the customer can test to confirm the requirement is successfully
implemented.
By testing the created AK on a VM running on a hypervisor.
7. Is there already an existing RFE upstream or in Red Hat bugzilla?
No
8. Does the customer have any specific timeline dependencies?
No
9. Is the sales team involved in this request and do they have any
additional input?
No
10. List any affected packages or components.
- Activation key
- Subscription-manager
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/6321 added
Updated by Eric Helms over 7 years ago
- Tracker changed from Bug to Feature
- Subject changed from Allow activation keys to enable product repos regardless of whether there is a subscription attached or not to Allow activation keys to enable product repos regardless of whether there is a subscription attached or not
- Category set to Activation Key
- translation missing: en.field_release set to 188
Updated by Justin Sherrill over 7 years ago
- Status changed from Ready For Testing to New
- translation missing: en.field_release changed from 188 to 114
Updated by Klaas D about 7 years ago
I tried the workaround suggested by sean in the bz - that only partly works for me. It works fine for everything covered by my primary redhat subscription but my rhscl subscriptions need to be enabled manually, my current workaround is to just use the first rhscl license inside kickstart and enable the corresponding repository, usually the first license is the temporary guest rhscl license :)
subscription-manager attach --pool=`subscription-manager list --all --available|grep -A 20 "Software Collections and Developer Toolset"|grep "Pool ID"|head -1| awk '{print $3}'`
subscription-manager repos --enable rhel-server-rhscl-<%= os_major %>-rpms
Greetings
Klaas
Updated by Klaas D about 7 years ago
I've been searching for a different approach for this issue, I've created a bug in candlepin for this:
https://bugzilla.redhat.com/show_bug.cgi?id=1441117
as a workaround I just put the product certs of all products I want to use into /etc/pki/product-defaults then auto-attach is taking care of it (I plan to make this based on the activation key used, but I have not finished that yet)