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.
Descriptionsthirugn@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:
Moving to POST since upstream bug http://projects.theforeman.org/issues/9898 has been closed
-------------
Christine Fouant
Applied in changeset commit:katello|c375db31b988918b37d740bfe9abf8f059bac758.
Comment 5sthirugn@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>"