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.
Document URL: https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/quick-start-guide/#registering_existing_system
Section Number and Name: section 7.1 registering an existing host
Describe the issue: in section 7.1, step 3 the user is informed to run the following to register an existing system.
# subscription-manager register --org $ORG --activationkey ak-Reg_To_Dev_EL7 --environment Default_Organization/DEV
Suggestions for improvement:
This command will not work for the following reasons:
- --environment _cant_ be used with activation keys. (There is no need to. Environment is implicitly part of what activation keys set)
- in section 6.6, we have the user create an activation key for the purpose of registering a system (which differs in naming from the above command)
- --environment requires lifecycle_environment/content_view and the above command uses organization/lifecycle_environment.
Additional information:
simply removing the --environment option from the command is sufficient to achieve the desired result (registering an existing system).