Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:
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.
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