Bug 1201425

Summary: Content Host registration should be more explicit in mentioning Organization and Activation key
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: Content ManagementAssignee: Christine Fouant <cfouant>
Status: CLOSED CURRENTRELEASE QA Contact: sthirugn <sthirugn>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bbuckingham, bkearney
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/9898
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 14:02:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description sthirugn@redhat.com 2015-03-12 16:53:57 UTC
Description of problem:
Content Host registration should be more explicit in mentioning Organization and Activation key

Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150311.1

How reproducible:
Always

Steps to Reproduce:
1. Go to Hosts -> Content Hosts -> Register Content Host
2. Review the displayed instructions for Content Host Registration

1. Select a Content Source:

2. Install the pre-built bootstrap RPM:

rpm -Uvh http://$mysat6host/pub/katello-ca-consumer-latest.noarch.rpm

3. Run subscription-manager in a console on the client host. You may use an Activation Key to register:

subscription-manager register --org="Default_Organization" --activationkey="activationkey1"

or authenticate with a username and password:

subscription-manager register --org="Default_Organization" --environment="Library"

4. Install katello-agent for remote actions and displaying errata information:

yum -y install katello-agent


Actual results:
Look at Step 3.  This looks like an instruction I can just copy and paste to my content host - Obviously 'activationkey1' is a non-existent activation key and is used just as an example

Expected results:
May be we should display Step 3 as follows or similar:

3. Run subscription-manager in a console on the client host. You may use an Activation Key to register:

subscription-manager register --org="Your Organization label" --activationkey="Your Activation Key"

or authenticate with a username and password:

subscription-manager register --org="Your Organization label" --environment="Library"

Additional info:

Comment 2 Christine Fouant 2015-03-25 14:58:53 UTC
Created redmine issue http://projects.theforeman.org/issues/9898 from this bug

Comment 3 Bryan Kearney 2015-04-08 20:05:56 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/9898 has been closed
-------------
Christine Fouant
Applied in changeset commit:katello|c375db31b988918b37d740bfe9abf8f059bac758.

Comment 5 sthirugn@redhat.com 2015-04-27 14:01:57 UTC
Verified.

Version Tested: 
Satellite-6.1.0-RHEL-6-20150424.0

Now it shows:
subscription-manager register --org="Default_Organization" --activationkey="<Activation Key Name>"

Comment 6 Bryan Kearney 2015-08-11 13:37:14 UTC
This bug is slated to be released with Satellite 6.1.

Comment 7 Bryan Kearney 2015-08-12 14:02:25 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.