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:
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:
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: 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: