Description of problem: Exception raised when registering/auto-subscribing when there are no service levels that cover all installed products Version-Release number of selected component (if applicable): master How reproducible: Always Steps to Reproduce: 1. Copy cert 100000000000002.pem to /etc/pki/product/ 2. Attempt to register the system via subscription-manager Actual results: GUI hangs on progress bar, and the following exception is raised and is in the log. Traceback (most recent call last): File "/usr/share/rhsm/subscription_manager/gui/registergui.py", line 971, in _watch_thread callback(retval) File "/usr/share/rhsm/subscription_manager/gui/registergui.py", line 515, in _on_get_service_levels_cb "this system."), parent=self.parent_window) AttributeError: 'SelectSLAScreen' object has no attribute 'parent_window' Expected results: No error occurs, and dialog is presented stating that there are no service levels that cover all installed products.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
*** Bug 841184 has been marked as a duplicate of this bug. ***
commit 93c65c65ef65429945b4e4e24b9545ac784f0037 Author: Michael Stead <mstead> Date: Mon Jul 16 16:10:07 2012 -0300 840637: Fixed missing reference to parent window.
Available in: subscription-manager-1.0.10-1+
Created attachment 602688 [details] A dialog stating that there are no service levels Marking verified [root@dhcp201-115 tmp]# rpm -qa | grep subscription-manager subscription-manager-migration-data-1.11.2.2-1.git.2.c3c8e22.el5 subscription-manager-firstboot-1.0.12-1.git.36.cb30843.el5 subscription-manager-migration-1.0.12-1.git.36.cb30843.el5 subscription-manager-1.0.12-1.git.36.cb30843.el5 subscription-manager-gui-1.0.12-1.git.36.cb30843.el5
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-2013-0033.html