Red Hat Bugzilla – 1614002 – Activation key with multiple pools for the same subscription and auto-attach no makes subscription-manager pick the sub multiple times
Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
Upon registrarion of a new system into Satellite, using an activation key that contains multiple pools for the same subscription and auto-attach NO, will result in the content host consuming the same subscription multiple times (one per repeated pool).
Version-Release number of selected component (if applicable):
subscription-manager: 1.20.11-1.el7_5
Red Hat Satellite 6.2.14
How reproducible:
always
Steps to Reproduce:
1. Create Activation Key and add same the same subscription from different pools
2. Set the activation key as "auto-attach NO"
3. Register a system
Actual results:
One subscription from every pool is picked up even if they belong to the same subscription
Expected results:
subscription-manager would only attach the required subscription once
Additional info:
As a workaround the exceeding subscriptions can be removed manually from the content hosts, or merge the multiple pools into one in the manifest manually to avoid the situation. However these options are not always available to an operator, or add operational complexity. Having subscription-manager to idnetify this situation automatically is preferred.
Hi Mauro,
I'm under the impression that an activation key with a list of pools specified and auto-attach set to NO will result in an attempted attachment to all of the pools so listed.
Given that my suggestion would be to set auto-attach to YES on that activation key. This will cause auto-attach to be run using only the given list of pools as input, which should result in far fewer attachments.
Cheers,
Chris