Bug 1399846 - section 7.1 registering an existing host
Summary: section 7.1 registering an existing host
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Quick Start Guide
Version: 6.2.4
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: Zac Dover
QA Contact: Lucie Jirakova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-29 21:54 UTC by Rich Jerrido
Modified: 2019-09-26 14:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-12 00:48:06 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Rich Jerrido 2016-11-29 21:54:11 UTC
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).

Comment 2 Andrew Dahms 2017-01-10 12:15:51 UTC
Assigning Lucie as the QA contact.

Lucie - can you take a look at the changes for this bug?

Comment 9 Andrew Dahms 2017-01-12 00:48:06 UTC
This content is live on the Customer Portal.

Closing.


Note You need to log in before you can comment on or make changes to this bug.