RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 746257 - “Man subscription-manager “Displays wrong example for activation key
Summary: “Man subscription-manager “Displays wrong example for activation key
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bryan Kearney
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel62 748554
TreeView+ depends on / blocked
 
Reported: 2011-10-14 14:52 UTC by spandey
Modified: 2015-04-23 23:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 17:25:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
edited manpage (28.86 KB, text/plain)
2011-10-17 15:57 UTC, Deon Ballard 		no flags Details
edited manpage #2 (28.85 KB, text/plain)
2011-10-17 23:18 UTC, Deon Ballard 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1695 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2011-12-06 01:23:29 UTC

Description spandey 2011-10-14 14:52:24 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Prerequisites:
Rhel6.2 client with following rpm 
subscription-manager-firstboot-0.96.15-1.el6.x86_64
.
subscription-manager-gnome-0.96.15-1.el6.x86_64.

subscription-manager-0.96.15-1.el6.x86_64
.

Steps to Repro : 

Execute following command on console to display subscription manager man page 

man subscription-manager 
check for activationkey info 

Expected Result : 
It should display no user and password is required for activation key registration  

Actual Result : 
subscription-manager register --username=admin --password=secret

              --org="IT Dept" –activationkey=1234abcd
Comment 3 John Sefler 2011-10-14 15:41:25 UTC 
Deon,
Just to help clarify... the REGISTER OPTIONS/--activationkey=KEYS section of the subscription-manager man page is pasted below.   In this section we'd like to remove "--username=admin --password=secret" from the example.  You could also add a note to the effect that the no username and password are needed when registering with an activationkey because the authentication is implied in the key.  <- Maybe Bryan or Will can help with that wording.




       --activationkey=KEYS
              Gives  a  comma-separated  list  of  product  keys  to  use to redeem or apply specific subscriptions to the machine. This is used generally for preconfigured
              machines, which may already have products installed and subscriptions allocated for that consumer.  For example:
              subscription-manager register --username=admin --password=secret
              --org="IT Dept" --activationkey=1234abcd

       Giving the org name is not necessary in hosted environments or infrastructures which have only a single organization.
Comment 4 Deon Ballard 2011-10-17 15:57:50 UTC 
Created attachment 528574 [details]
edited manpage

I changed the --activationkey example as indicated, and I also added a little note about the authentication and --org stuff, also as indicated.
Comment 6 John Sefler 2011-10-17 22:15:22 UTC 
NEEDINFO from bkearney or wpoteat...

When the --activationkey option is used, it is not necessary to use the --username and --password options, because the user information and authentication is implicit in the activation key.

^^^
Is the "because...." clause of Deon's re-worded description from attachment 528574 [details] of the activationkey option accurately stated?  I don't think "the user information and" should be in this sentence.
Comment 7 Bryan Kearney 2011-10-17 23:10:29 UTC 
The user information is not in the key but the authentication information is.
Comment 8 Deon Ballard 2011-10-17 23:18:59 UTC 
Created attachment 528673 [details]
edited manpage #2

Removed the user reference. Users are gone and only authentication remains.
Comment 9 James Bowes 2011-10-18 13:37:20 UTC 
fixed in rhel6.2 eafe19ba
and master 7615c9054817c6
Comment 11 John Sefler 2011-10-18 16:28:29 UTC 
Verifying Version...
[root@jsefler-onprem-62server ~]# rpm -q subscription-manager
subscription-manager-0.96.15-1.git.7.fbf42c7.el6.x86_64

[root@jsefler-onprem-62server ~]# man subscription-manager

...SNIP...

       --activationkey=KEYS
              Gives  a  comma-separated  list of product keys to use to redeem or apply specific subscriptions to the machine. This is used generally for preconfigured machines, which may already have products installed and subscriptions allocated for that consumer.

       When the --activationkey option is used, it is not necessary to use the --username and --password options, because the authentication information is implicit in the activation key.

       In hosted or single organization environments, it is not necessary to specify an organization with the --org option, but in multi-organization environments, this is required.

       For example:
              subscription-manager register --org="IT Dept" --activationkey=1234abcd

       Giving the org name is not necessary in hosted environments or infrastructures which have only a single organization.

...SNIP...


^^^ THIS MAN PAGE DESCRIPTION FOR REGISTER OPTION --activationkey IS GOOD
Moving to VERIFIED
Comment 12 errata-xmlrpc 2011-12-06 17:25:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1695.html
Note You need to log in before you can comment on or make changes to this bug.