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.
Description of problem:
Trying to rebuild a host fails when the host is using an activation key with the limit set as 1. The re-build does not re-use the activation key already attached to the host.
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.9
How reproducible:
Always
Steps to Reproduce:
1: Create an activation key with an host limit to 1
2: Create an Host group and attach the activation key
3: Deploy/create a new host using host group
4: Confirm activation key host limit usage is "1 of 1"
5: Select the newly deployed host in all hosts and choose/click build (To rebuild host)
The re-build will fail because the activation key limit is 1. Expected is that it re-uses the activation key
Actual results:
the rebuild fails as the activation key limit is 1.
Expected results:
The Activation key should be reused by the host.
Additional info:
A temporary workaround is to increase the activation key limit by 1.
1: Raise the host limit by one on the activation key
2: Confirm activation key host limit usage is "1 of 2"
3: Select the newly deployed host in all hosts and choose/click build (To rebuild host)
The re-build of the host will succeed...
4: Check and verify activation key host limit usage has not increased and still is "1 of 2"