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: Activation keys are useless without lifecycle environment set.

So why not make this parameter mandatory? Or make "Library" the default one...


How reproducible: always/deterministic


Steps to Reproduce:
  1. Create activation key without environment (via api you can even
     set content view without setting environment).
  2. Try to use it

Actual results:

# subscription-manager register --org="Red_Hat_SatTeam" --activationkey="1-akakakak"
At least one activation key must have a lifecycle environment and content view assigned to it
# subscription-manager register --org="Red_Hat_SatTeam" --activationkey="1-akakakak" --environment="Library"
Error: Activation keys do not allow environments to be specified.


Expected results: Either Library is used by default OR you can specify --environment with activation key OR it would not be possible to create useless activation key

aditional info: sat6-Satellite-6.0.4-RHEL-6-20140730.0-Satellite-x86_64-dvd1.iso

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.

Last week, I heard that activationkey can be paired in subscription-manager commands like:

subscription-manager register --activationkey PREMIUM-JBOSS-STACK --activationkey PRODUCTION-ENVIRONMENT

So one activation key will hold my subscriptions and other will hold my environments.  I never tried this though.  

If this is a valid scenario, then it is valid to allow activation key to be created without environment or content view.

This is working as intended. Multiple activation keys may be specified to subscription-manager and at least one must reference a content view.