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:
# rhn-migrate-classic-to-rhsm --help | grep rhn-migrate
Usage: /usr/sbin/rhn-migrate-classic-to-rhsm [--force|--cli-only|--help|--no-auto]
^ That usage statement is verbose. To be more consistent with the usage statement of other rhsm tools, I suggest this:
Usage: rhn-migrate-classic-to-rhsm [OPTIONS]
Version-Release number of selected component (if applicable):
# rpm -q --whatprovides `which rhn-migrate-classic-to-rhsm`
subscription-manager-migration-0.99.8-1.git.13.1ecb596.el6.x86_64
Actual results:
[root@jsefler-r63-server ~]# rhn-migrate-classic-to-rhsm --help
Usage: /usr/sbin/rhn-migrate-classic-to-rhsm [--force|--cli-only|--help|--no-auto]
Options:
-f, --force Ignore channels not available on RHSM
-c, --cli-only Don't launch the GUI tool to subscribe the system, just use
the CLI tool which will do it automatically
-n, --no-auto Don't execute the autosubscribe option while registering
with subscription manager.
-h, --help show this help message and exit
# rpm -q subscription-manager-migration
subscription-manager-migration-0.99.8-1.git.16.f7525bc.el6.x86_64
# rhn-migrate-classic-to-rhsm --help | grep rhn-migrate
Usage: /usr/sbin/rhn-migrate-classic-to-rhsm [OPTIONS]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Do we really need that full path?
Moving back to NEW/FailedQA
Moving bug to verified..
RPM used:
[root@dhcp201-162 ~]# rpm -qa | grep subscription-manager
subscription-manager-migration-0.99.8-1.git.8.cc12bc5.el6.x86_64
subscription-manager-0.99.8-1.git.8.cc12bc5.el6.x86_64
subscription-manager-firstboot-0.99.8-1.git.8.cc12bc5.el6.x86_64
subscription-manager-migration-data-1.12.1-1.git.4.7b6cf92.el6.noarch
subscription-manager-debuginfo-0.99.8-1.el6.x86_64
subscription-manager-gnome-0.99.8-1.git.8.cc12bc5.el6.x86_64
[root@dhcp201-162 ~]# rhn-migrate-classic-to-rhsm --help
Usage: rhn-migrate-classic-to-rhsm [OPTIONS]
Options:
-f, --force Ignore channels not available on RHSM
-c, --cli-only Don't launch the GUI tool to subscribe the system, just use
the CLI tool which will do it automatically
-n, --no-auto Don't execute the autosubscribe option while registering
with subscription manager.
-h, --help show this help message and exit
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-2012-0804.html
Description of problem: # rhn-migrate-classic-to-rhsm --help | grep rhn-migrate Usage: /usr/sbin/rhn-migrate-classic-to-rhsm [--force|--cli-only|--help|--no-auto] ^ That usage statement is verbose. To be more consistent with the usage statement of other rhsm tools, I suggest this: Usage: rhn-migrate-classic-to-rhsm [OPTIONS] Version-Release number of selected component (if applicable): # rpm -q --whatprovides `which rhn-migrate-classic-to-rhsm` subscription-manager-migration-0.99.8-1.git.13.1ecb596.el6.x86_64 Actual results: [root@jsefler-r63-server ~]# rhn-migrate-classic-to-rhsm --help Usage: /usr/sbin/rhn-migrate-classic-to-rhsm [--force|--cli-only|--help|--no-auto] Options: -f, --force Ignore channels not available on RHSM -c, --cli-only Don't launch the GUI tool to subscribe the system, just use the CLI tool which will do it automatically -n, --no-auto Don't execute the autosubscribe option while registering with subscription manager. -h, --help show this help message and exit