Ticket #975 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

should handle https:// missing from `bcfg2 -S` better

Reported by: Arto Jantunen <[email protected]…> Owned by: desai
Priority: minor Milestone: Bcfg2 1.1.2 Release (Bugfix)
Component: bcfg2-client Version: 1.0
Keywords: Cc:


This was originally filed in the Debian BTS as Bug#608622 (see ), the original report follows:

I feel this IOError should be caught, ideally suggesting the use of https://.

epicfail:/etc# bcfg2 -q -v -n -S Traceback (most recent call last):

File "/usr/sbin/bcfg2", line 300, in <module>

File "/usr/sbin/bcfg2", line 166, in run

allowedServerCNs = self.setupserverCN?)

File "/usr/lib/pymodules/python2.6/Bcfg2/", line 314, in ComponentProxy?

return xmlrpclib.ServerProxy?(newurl, allow_none=True, transport=ssl_trans)

File "/usr/lib/python2.6/", line 1463, in init

raise IOError, "unsupported XML-RPC protocol"

IOError: unsupported XML-RPC protocol

This reaches the server: epicfail:/etc# bcfg2 -q -v -n -S


Change History

comment:1 Changed 12 years ago by desai

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

A fix has been committed in [d9cd51cc7449902361611a0cef7cd4b71c57f11f] and will be included in 1.2.0pre1

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


Add a comment

Modify Ticket

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

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

Note: See TracTickets for help on using tickets.