Bug 1196385

Summary:	rhn-migrate-classic-to-rhsm man page needs a description for new --activation-key option
Product:	Red Hat Enterprise Linux 6	Reporter:	John Sefler <jsefler>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED ERRATA	QA Contact:	John Sefler <jsefler>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.7	CC:	awood, dgoodwin, skallesh, wpoteat
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-22 06:53:05 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:
Bug Depends On:
Bug Blocks:	1125249

Description John Sefler 2015-02-25 21:09:29 UTC

Description of problem:
After implementation of bug 1154375, the rhn-migrate-classic-to-rhsm man page needs an update to include a description for the new --activation-key option


Version-Release number of selected component (if applicable):
[root@jsefler-os6 ~]# rpm -q subscription-manager
subscription-manager-1.14.1-1.git.37.61e53ff.el6.x86_64


How reproducible:


Steps to Reproduce:
[root@jsefler-os6 ~]# rhn-migrate-classic-to-rhsm --help | grep -i "activation" -A1
  --activation-key=ACTIVATION_KEYS
                        activation key to use for registration (can be
                        specified more than once)
[root@jsefler-os6 ~]# man rhn-migrate-classic-to-rhsm | grep -i "activation"
[root@jsefler-os6 ~]# 


Actual results:
none

Expected results:
expected a man page description similar to the one used in the subscription-manager man page...

       --activation-key=KEYS
              Gives  a comma-separated list of product keys to use to
              redeem or apply specific subscriptions to  the  system.
              This  is  used  for  preconfigured  systems  which  may
              already have products installed.  Activation  keys  are
              issued  by  an  on-premise subscription management ser-
              vice, such as Subscription Asset Manager.

              When the --activation-key option is used, it is not nec-
              essary  to  use  the --destination-user and --destination-password= options,
              because the authentication information is  implicit  in
              the activation key.


Additional info:

Comment 1 Alex Wood 2015-04-08 14:11:43 UTC

commit 186c2faa388969b3752369a094b31a5e0e81fa64
Author: Alex Wood <awood>
Date:   Thu Feb 26 14:58:23 2015 -0500

    1196385: Add --activation-key option to migration man page.

Comment 3 Shwetha Kallesh 2015-04-13 08:22:50 UTC

Marking verified!!

[root@dhcp35-135 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.47-1
subscription management rules: 5.14
subscription-manager: 1.14.3-1.el6
python-rhsm: 1.14.2-1.el6


[root@dhcp35-236 ~]# man rhn-migrate-classic-to-rhsm | grep -i "activation"
       [--activation-key=ACTIVATION_KEY] | [--help]
              Sets an activation key to use during registration  to  the  sub-
              scription management service.  Use of an activation key requires


Complete Description in man page:

 --activation-key=ACTIVATION_KEY
              Sets  an activation key to use during registration to the subscription management service.  Use of an activation key requires the user to
              supply the organization that the system will be registered to.  This option may be supplied multiple times.

Comment 4 errata-xmlrpc 2015-07-22 06:53:05 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.

https://rhn.redhat.com/errata/RHBA-2015-1345.html