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:
[en_US] [RHSM Firstboot] Exception Occurred when Forward in Choose Service page after registered and run in firstboot again.
Version-Release number of selected component (if applicable):
subscription-manager-1.12.14-7.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Register the system via RHSM GUI or Firstboot.
2. Run from terminal: firstboot --reconfig
3. Next to the Choose Service page.
4. Select Red Hat Subscription Management and Foward.
Actual results:
Exception Occurred when Forward in Choose Service page after registered and run in firstboot again.
Expected results:
No such Exception.
Additional info:
Please see the attached screen-shot and log file.
(for easier reference)
firstboot 1.110.15 exception report
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/firstboot/interface.py", line 105, in _nextClicked
self.advance()
File "/usr/lib/python2.6/site-packages/firstboot/interface.py", line 148, in advance
result = module.apply(self, self.testing)
File "/usr/share/rhn/up2date_client/firstboot/rhn_choose_server_gui.py", line 58, in apply
while not interface.moduleList[i].__module__.startswith('rhsm_'):
IndexError: list index out of range
Any other logs from this (firstboot log maybe?).
I think on this crash, there are no rhsm module available to firstboot, because the system is already registered? The rhsm_modules are skipped if the system is registered (via submans firstboot_base:RhsmFirstbootModule.shouldAppear().
In that case, the line 58 above eventually walks off the end of the modules list without finding a rhsm module and throws the index error. But not having rhsm modules in the modules list is a valid scenario (either because of running firstboot more than once, or if the system was registered in the kickstart).
Going to bounce this to rhn-client-tools for that.
Verified with package rhn-setup-gnome-1.0.0.1-32.el6.noarch.rpm
Tested all combinations:
1) unregister to rhn X unregister to rhsm
2) register to rhn X unregister to rhsm
3) unregister to rhn X register to rhsm
3) register to rhn X register to rhsm
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.
https://rhn.redhat.com/errata/RHBA-2015-1395.html