Description of problem:
I had get an error message while I run up2date
Traceback (most recent call last):
File "/usr/share/rhn/up2date_client/gui.py", line 752, in
self.hardware = hardware.Hardware()
File "/usr/share/rhn/up2date_client/hardware.py", line 531, in
ret = read_network()
File "/usr/share/rhn/up2date_client/hardware.py", line 359, in
hostname, ipaddr = findHostByRoute()
File "/usr/share/rhn/up2date_client/hardware.py", line 328, in
(server, port) = string.split(server_port, ':')
File "/usr/lib/python2.2/string.py", line 122, in split
return s.split(sep, maxsplit)
AttributeError: 'NoneType' object has no attribute 'split'
I cannot register any profile to use up2date. Does anyone know how to
solve it? Many thanks!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
If you have not already, you would be wise to contact support, at
800-REDHAT1, or http://www.redhat.com/support, about this matter. You
will need your up-to-date entitlement information for this purpose.
Created attachment 105815 [details]
patch for workaround
workaround patch. see bug comments
sorry, this comment was intended to precede the above patch...
i had the same problem. apparently it has to do with the
'self.hardware' object not containing a field named 'class' for every
'hw' in the iteration (please excuse my lack of python-oriented
terminology -- i'd never seen python before this).
a *work-around* is as follows (see one-liner diff in attachment [well,
essentially one-liner, python doesn't diff well with all that
essential formatting...]), simply check to see whether the current
'hw' object in the loop iteration has a 'class' key.
this DOES NOT fix whatever is causing the self.hardware object to
contain entries without the 'class' field. for that, i unfortunately
have no suggestion or idea.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.