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:
When adding subscriptions from an available pool more than once (adding a subset each time), subscription-manager registration fails if one of the pools in an AK is full.

Version-Release number of selected component (if applicable):
6.0.3 BETA

How reproducible:


Steps to Reproduce:
1. Create a manifest in the customer portal, add a subset of one RHEL w/ Smart Management subscription, e.g. 1 out of the available X.

2. Import the sub to Satellite, add it to an AK, and register a host to it.

3. Go to the portal, and add the remaining subs, add RHEL sub to existing AK


Actual results:
Failure - it reports no available subscriptions for pool XXXXXXX>

Expected results:
System is registered

Additional info:

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

If I am reading this correctly, this is the correct behavior: All subscriptions associated with an activation key are applied to a content host registering. If any of the subs fail to apply, the registration fails. Subs are not optional.

Please close this as not a bug if this is what is being reported.

Subscriptions of the same kind, e.g. 'Red Hat Enterprise Linux w/ Smart Management' should be treated as a bucket, otherwise a customer won't be able to purchase more subscriptions and add them to the same activation key.

*** This bug has been marked as a duplicate of bug 1126924 ***