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 818767 - man page for rhn-migrate-classic-to-rhsm should note that additional subscription-manager-migration-data must be installed
Summary: man page for rhn-migrate-classic-to-rhsm should note that additional subscrip...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Bryan Kearney
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks: 738066
TreeView+ depends on / blocked
 
Reported: 2012-05-03 22:20 UTC by John Sefler
Modified: 2012-09-18 11:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 12:57:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0804 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2012-06-19 19:51:31 UTC

Description John Sefler 2012-05-03 22:20:03 UTC 
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
subscription-manager-migration-0.99.16-1.el6.x86_64
[root@bigisis ~]# man -P cat rhn-migrate-classic-to-rhsm | grep Version
Version 0.2                     December 8 2011 rhn-migrate-classic-to-rhsm(8)
[root@bigisis ~]# 


How reproducible:


Steps to Reproduce:
[root@bigisis ~]# man -P cat rhn-migrate-classic-to-rhsm | grep -i data
[root@bigisis ~]# 

^^ No references to data at all.  Expected something in the man page to tell me to yum install subscription-manager-migration-data.
Comment 1 Deon Ballard 2012-05-04 01:37:41 UTC 
Committed into the 6.3 branch:
52582cbe51d67bdbc45b82c9ff020c2b9644e77e

And committed into master:
db5910e1247f4f92d270e53816f8c20a55589bcd

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?
Comment 4 John Sefler 2012-05-10 22:26:21 UTC 
Verifying Version....

[root@ibm-ls21-03 ~]# rpm -q subscription-manager-migration
subscription-manager-migration-0.99.17-1.el6.i686


Snippets from...
[root@ibm-ls21-03 ~]# man -P cat rhn-migrate-classic-to-rhsm
<---SNIP--->
       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.
<---SNIP--->
<---SNIP--->
       subscription-manager-migration-data.rpm
              The  package which contains the mappings for the migration
              script to migrate channels to the appropriate product cer-
              tificates.
<---SNIP--->
Version 0.3                       May 3, 2012   rhn-migrate-classic-to-rhsm(8)
[root@ibm-ls21-03 ~]# 


VERIFIED: Man page for rhn-migrate-classic-to-rhsm dictates that additional subscription-manager-migration-data must be installed.
Comment 6 errata-xmlrpc 2012-06-20 12:57:13 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-2012-0804.html
Note You need to log in before you can comment on or make changes to this bug.