Bug 614389 - registering shows error: global name 'xmlrpclib' is not defined
Summary: registering shows error: global name 'xmlrpclib' is not defined
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rhn-client-tools
Version: 12
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
Assignee: Miroslav Suchý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: space11
TreeView+ depends on / blocked
 
Reported: 2010-07-14 11:33 UTC by Petr Sklenar
Modified: 2010-07-15 08:30 UTC (History)
1 user (show)

Fixed In Version: rhn-client-tools-1.1.11-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-15 08:30:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Petr Sklenar 2010-07-14 11:33:50 UTC
Description of problem:
registering fedora12 inbto spacewalk.nightly shows error: global name 'xmlrpclib' is not defined

Version-Release number of selected component (if applicable):
Fedora-12 with
rhn-setup-1.1.10-1.fc12.noarch
rhn-client-tools-1.1.10-1.fc12.noarch


How reproducible:
always

Steps to Reproduce:
0.
have a spacewalk today's nightly
activation key was universal default into my custom channel

1. # rhnreg_ks --username=admin --password=admin --server=http://hp-dl580g5-01.rhts.eng.bos.redhat.com/XMLRPC
libvir: Remote error : unable to connect to '/var/run/libvirt/libvirt-sock': No such file or directory
An error has occurred:
<type 'exceptions.NameError'>
  
Actual results:
tail /var/log/up2date
[Wed Jul 14 07:23:04 2010] up2date 
Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 205, in <module>
    cli.run()
  File "/usr/share/rhn/up2date_client/rhncli.py", line 107, in run
    except xmlrpclib.ProtocolError, e:
<type 'exceptions.NameError'>: global name 'xmlrpclib' is not defined

Expected results:
there is no such a error

Additional info:

Comment 1 Miroslav Suchý 2010-07-15 08:30:30 UTC
Fixed in commit 6424c6e1a47bff8cd1d1f834af814f0c541ee1cb
Will be fixed in F14.


Note You need to log in before you can comment on or make changes to this bug.