Red Hat Bugzilla – Bug 449761
rhn_register crashes in "/usr/share/rhn/up2date_client/tui.py"
Last modified: 2013-01-22 11:27:21 EST
Description of problem:
On a newly installed RHES5 system (long after firstboot), I start rhn_register.
Everything works fine up to the point where rhn_register tries to push
information about the host to the RHN (note that a host with the same name
already exists at the RHN as I'm actually trying to upgrade the machine from
RHES4 to RHES5 and I'm not sure whether I'm proceeding correctly, but that is
another problem). At some point during the push, the program stops:
[root@misato bin]# rhn_register
An error has occurred:
See /var/log/up2date for more information
In /var/log/up2date, we see:
[Tue Jun 3 14:01:53 2008] rhn_register
Traceback (most recent call last):
File "/usr/sbin/rhn_register", line 82, in ?
File "/usr/share/rhn/up2date_client/rhncli.py", line 65, in run
sys.exit(self.main() or 0)
File "/usr/sbin/rhn_register", line 64, in main
File "/usr/share/rhn/up2date_client/tui.py", line 2011, in main
File "/usr/share/rhn/up2date_client/tui.py", line 1883, in run
win = self.windows[index](self.screen, self)
File "/usr/share/rhn/up2date_client/tui.py", line 1520, in __init__
rw = ReviewWindow(self.screen, self.tui, reg_info)
File "/usr/share/rhn/up2date_client/tui.py", line 1564, in __init__
if self.tui.activate_result.getStatus() == \
exceptions.AttributeError: 'dict' object has no attribute 'getStatus'
But after that also:
[Tue Jun 3 14:09:43 2008] up2date logging into up2date server
[Tue Jun 3 14:09:44 2008] up2date successfully retrieved authentication token
from up2date server
Furthermore, trying to start rhn_register again yields:
Red Hat Network Location: https://xmlrpc.rhn.redhat.com/XMLRPC
RHN Login: mplify
System ID: ID-1012640252
So the problem is not "blocking"
Version-Release number of selected component (if applicable):
rhn-setup-0.4.17-8.el5 (to which rhn_register belongs)
yum-rhn-plugin-0.5.3-6.el5 (to which up2date belongs)
from what I see, the only time this could happen is if your client is not able to communicate with the server or if server is returning an error code other than 0 or 1.
Multiple cases in which this could happen:
* It could be the installation number you entered or the rogId in an existing registration could not be validated.
* or while you were trying RHN was in an outage mode or your client could not communicate with RHN and caused an CommunicationError exception.
Could you give it a try again and see if this happens again? also make sure you're using the right installation number while activating your client.
The machine is currently correctly registered, so I think I cannot re-register it. I have a few RHEL4 machines that still have to be upgraded to RHEL5 (though I don't know when), so I can try then?
Currently there is not enough information here for us to replicate and attempts so far have not been able too.
If this is still an open issue for you, please open a support ticket giving
details and we can assist to investigate further.
Development Management has reviewed and declined this request. You may appeal
this decision by reopening this request.