Copied the registration from my backup, on a clean re-install of 7.2, followed
by a upgrade to RH 7.3 -- got this:
[root@couch root]# up2date
Migrating network settings from rhn_register
Traceback (innermost last):
File "/usr/sbin/up2date", line 1169, in ?
File "/usr/sbin/up2date", line 364, in main
File "/usr/share/rhn/up2date_client/up2date.py", line 556, in updateLoginInfo
loginInfo = login()
File "/usr/share/rhn/up2date_client/up2date.py", line 487, in login
loginInfo = doCall(server.up2date.login, systemId)
File "/usr/share/rhn/up2date_client/up2date.py", line 426, in doCall
ret = apply(method, args, kwargs)
File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 689, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 746, in __request
File "/usr/lib/python1.5/site-packages/xmlrpclib.py", line 638, in request
File "/usr/lib/python1.5/site-packages/cgiwrap.py", line 591, in send_http
File "/usr/lib/python1.5/httplib.py", line 86, in send
File "/usr/lib/python1.5/httplib.py", line 184, in send
TypeError: argument 1: expected string without null bytes, string found
[root@couch root]# rpm -q rhn_register up2date
[root@couch root]# cat /etc/redhat-release
Red Hat Linux release 7.3 (Valhalla)
Please let me know if you need more. I an leery of uploading my
/etc/sysconfig/rhn/systemid as an attachment.
ugh, uhmm.. off hand, no clue... I'll dig deeper and see
if I find anything.
Did you do a normal upgrade from Red Hat 7.2 to 7.3 using the installer, or
manually upgrade redhat-release then run up2date -u? The latter seems to work
in many cases, but it is untested (unsupported), and likely to cause problems in
some cases like a version downgrade or orphans leftover due to obsoletism.
straight installer upgrade from CD boot ... text mode
not seen with current content -- closing
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.