[Spacewalk-list] Errors when trying to add SLES 11 SP4 to SW

[Daryl Rose]

I finally found an answer for this issue.

I found this post on Redhat.com

https://www.redhat.com/archives/spacewalk-list/2015-July/msg00136.html

I had to rename:

def idn_pune_to_unicode(hostname): to def idn_puny_to_unicode(hostname):

and

def idn_ascii_to_pune(hostname): to def idn_ascii_to_puny(hostname):

Once I made the changes, I was able to register the server just fine.

What confuses me is; why would I have to do this?  I've successfully registered 86 SLES 11 SP4 servers, and this was a clone of a server that was previously registered.  So what changed?  Anyone have any thoughts?

Thanks

Daryl



________________________________
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> on behalf of Daryl Rose <darylrose at outlook.com>
Sent: Monday, December 21, 2015 1:35 PM
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] Errors when trying to add SLES 11 SP4 to SW



I just cloned a SLES 11 SP4 server.  The original server had already been registered to my SW server.  However, I get errors when registering the newly cloned machine:


# rhnreg_ks --serverUrl=https://<spwalk server>/XMLRPC --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT --activationkey=1-83113b0405126dd5e8ed413d321190eb
Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 25, in <module>
    from rhn.connections import idn_puny_to_unicode
ImportError: cannot import name idn_puny_to_unicode



I completely cleaned out all of the old registration information.  Stopped started SW services, even rebooted the server.  But I still get the same error.


I'm using SW v 2.3.


Any suggestions?


Thanks


Daryl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20151223/d2617929/attachment.htm>