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:
The way activation-keys work are that you need to create an activation-key per physical/virtual subscription type per content-set per content view per lifecycle environment. This results in an explosion of needed activation keys for each possible situation and is unworkable.

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


How reproducible:
Build a setup with multiple lifecycle environments, content-views and use different subscriptions, different enabled repos and multiple host-groups. Now create activation-keys that can subscribe systems for each situation. Count the nr of activation keys created.

Steps to Reproduce:
1.
2.
3.

Actual results:
A large amount

Expected results:
A small amount

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.

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