Modify

Ticket #11 (closed defect: fixed)

Opened 14 years ago

Last modified 13 years ago

Traceback

Reported by: leggett@… Owned by: desai
Priority: minor Milestone: Bcfg2 0.8.1 Release
Component: bcfg2-client Version:
Keywords: Cc:

Description

Version: 0.8.0pre1

[root@nmpdr-compute-2:/var/db/bcfg-new/Metadata]$ /usr/sbin/bcfg2 -q -n Traceback information (please include in any bug report): File /usr/sbin/bcfg2, line 53, in run_method

ret = apply(method, (self.setupuser?,

xmlrpclib.ProtocolError?: <ProtocolError? for nmpdr-compute-2.uchicago.edu:6789/RPC2: -1 >

File /usr/lib/python2.3/xmlrpclib.py, line 1029, in call

return self.send(self.name, args)

xmlrpclib.ProtocolError?: <ProtocolError? for nmpdr-compute-2.uchicago.edu:6789/RPC2: -1 >

File /usr/lib/python2.3/xmlrpclib.py, line 1316, in request

verbose=self.verbose

xmlrpclib.ProtocolError?: <ProtocolError? for nmpdr-compute-2.uchicago.edu:6789/RPC2: -1 >

File /usr/lib/python2.3/xmlrpclib.py, line 1070, in request

headers

xmlrpclib.ProtocolError?: <ProtocolError? for nmpdr-compute-2.uchicago.edu:6789/RPC2: -1 >

Fatal error: An unexpected failure occurred in configuration download

Attachments

Change History

comment:1 Changed 14 years ago by desai

  • Status changed from new to assigned
  • Milestone set to Bcfg2 0.8.1 Release

comment:2 Changed 14 years ago by desai

This should be handled more cleanly on the client side.

comment:3 Changed 14 years ago by desai

  • Status changed from assigned to closed
  • Resolution set to fixed

I merged in the current xmlrpc proxy code from cobalt into bcfg, and added error remapping from xmlrpclib.ProtocolError? -> xmlrpclib.Fault(20)

Fixed in revision [dfcd59780e947e448b2a51647fc01b72c8c9eabd] (SVN r1725)

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.