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.
DescriptionVedashree Deshpande
2019-07-10 10:11:31 UTC
Description of problem:
As per the https://access.redhat.com/solutions/3177511 we need to have two, one empty and one with subscriptions added activation keys to subscribe a system at the time of system building.
Version-Release number of selected component (if applicable):
Any satellite 6.
How reproducible:
When building a system attach only one activation key, the system will remain unentitled, even if the Activation Key has subscriptions and/or the auto-attach is enabled.
Actual results:
Need to add the second empty AK for the successful subscription.
Expected results:
Only one AK should be enough.
Additional info:
Reference: https://bugzilla.redhat.com/show_bug.cgi?id=1265125
Comment 3Vedashree Deshpande
2019-07-10 13:08:16 UTC
Information provided by the customer:
~~~
The bug only happens if you have activation keys with virt-who (Datacenter License) subscriptions assigned.
You only need the temporary subscriptions in that case.
Normal subscriptions will not have the same issue because they will assigned directly during the installation.
~~~
How to reproducible:
1. Create virt-who configuration for ESX Server
2. Attach "Red Hat Enterprise Linux for Virtual Datacenters, Standard" License to the ESX Hosts
3. Create Activation Key with virt-who Hosts and attach it to a Hostgroup
4. attach redhat_register snippet to provisioning template (if not already done)
5. Create a new VM running on one of the licensed hosts
6. execute "subscription-manager list" to validate attached subscription
Result: unsusbscribed
Expected Result: Subscribed with temporary subscription
Workaround: Attach another empty activation key without any configuration to the same hostgroup to get temporary subscription during installation.
Cole is the new Component owner for Activation Keys, assigning to him.
Cole, let me know if you have any questions on these or need help verifying them.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.