Red Hat Bugzilla – Bug 818767
man page for rhn-migrate-classic-to-rhsm should note that additional subscription-manager-migration-data must be installed
Last modified: 2012-09-18 07:06:35 EDT
Description of problem:
Because subscription-manager-migration can be installed without subscription-manager-migration-data (both of which are not installed by default), it is possible to run rhn-migrate-classic-to-rhsm and fail; see reference bug 816377 and bug 811779. Unfortunately the user is not told via the failure messages what to do. Reading the man page also does not tell the user what to do.
We need an extra blurb in the man page for rhn-migrate-classic-to-rhsm (and install-num-migrate-to-rhsm too) that somehow states that package subscription-manager-migration-data is required for the migration tools to be successful.
Version-Release number of selected component (if applicable):
[root@bigisis ~]# rpm -q subscription-manager-migration
[root@bigisis ~]# man -P cat rhn-migrate-classic-to-rhsm | grep Version
Version 0.2 December 8 2011 rhn-migrate-classic-to-rhsm(8)
Steps to Reproduce:
[root@bigisis ~]# man -P cat rhn-migrate-classic-to-rhsm | grep -i data
^^ No references to data at all. Expected something in the man page to tell me to yum install subscription-manager-migration-data.
Committed into the 6.3 branch:
And committed into master:
Sefler, I just added a couple of sentences at the beginning, in the description, that subscription-manager-migration-data is required for the scripts to work, and then I added it to the file list at the end. Think that's good enough, or should I figure out how to make it more obvious?
[root@ibm-ls21-03 ~]# rpm -q subscription-manager-migration
[root@ibm-ls21-03 ~]# man -P cat rhn-migrate-classic-to-rhsm
This script migrates configuration, from a channel-based sub-
scription framework to a certificate-based subscription frame-
work. While the rhn-migrate-classic-to-rhsm script performs the
migration operation, the data used to map the channels to the
corresponding product certificates is defined in the subscrip-
tion-manager-migration-data package. The subscription-manager-
migration-data package must be installed before the rhn-migrate-
classic-to-rhsm script can be run successfully.
The package which contains the mappings for the migration
script to migrate channels to the appropriate product cer-
Version 0.3 May 3, 2012 rhn-migrate-classic-to-rhsm(8)
VERIFIED: Man page for rhn-migrate-classic-to-rhsm dictates that additional subscription-manager-migration-data must be installed.
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.