Hide Forgot
Description of problem: When the subscription-manager-migration package was first released with rhel58, the new install-num-migrate-to-rhsm tool depends on instnum.py which was provided by rhel-instnum-1.0.9-1.el5. Now in rhel63, there is no install (nor brew build) of rhel-instnum package and therefore we get a traceback when we try to run install-num-migrate-to-rhsm as shown in the steps to reproduce below. Version-Release number of selected component (if applicable): [root@jsefler-r63-server ~]# rpm -q subscription-manager-migration subscription-manager-migration-0.99.7-1.el6.x86_64 How reproducible: Steps to Reproduce: [root@jsefler-r63-server ~]# install-num-migrate-to-rhsm --dryrun --instnumber 123 Traceback (most recent call last): File "/usr/sbin/install-num-migrate-to-rhsm", line 26, in <module> from instnum import InstallationNumber, InstallationNumberError ImportError: No module named instnum Actual results: ^^ Expected results: Could not parse the installation number: Unsupported string length Additional info:
There is no installation number in RHEL6. https://access.redhat.com/kb/docs/DOC-42509
reopening, we need to ensure the script is not installed on el6 systems.
*** Bug 795294 has been marked as a duplicate of this bug. ***
7b4cb1a 0.99.7+ master
moving to verified RPM used: [root@dhcp201-162 ~]# rpm -qa | grep subscription-manager subscription-manager-migration-0.99.8-1.git.22.c4b5c6a.el6.x86_64 subscription-manager-gnome-0.99.8-1.git.22.c4b5c6a.el6.x86_64 subscription-manager-firstboot-0.99.8-1.git.22.c4b5c6a.el6.x86_64 subscription-manager-debuginfo-0.99.8-1.el6.x86_64 subscription-manager-0.99.8-1.git.22.c4b5c6a.el6.x86_64 subscription-manager-migration-data-1.12.1-1.git.5.4a24dad.el6.noarch [root@dhcp201-162 ~]# rpm -ql subscription-manager-migration /usr/sbin/rhn-migrate-classic-to-rhsm /usr/share/doc/subscription-manager-migration-0.99.8 /usr/share/doc/subscription-manager-migration-0.99.8/LICENSE /usr/share/man/man8/rhn-migrate-classic-to-rhsm.8.gz
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