Ticket #975 (closed defect: fixed)
should handle https:// missing from `bcfg2 -S` better
| Reported by: | Arto Jantunen <viiru@…> | Owned by: | desai |
|---|---|---|---|
| Priority: | minor | Milestone: | Bcfg2 1.1.2 Release (Bugfix) |
| Component: | bcfg2-client | Version: | 1.0 |
| Keywords: | Cc: |
Description
This was originally filed in the Debian BTS as Bug#608622 (see http://bugs.debian.org/608622 ), the original report follows:
I feel this IOError should be caught, ideally suggesting the use of https://.
epicfail:/etc# bcfg2 -q -v -n -S kgoetz.selfip.net:6789 Traceback (most recent call last):
File "/usr/sbin/bcfg2", line 300, in <module>
client.run()
File "/usr/sbin/bcfg2", line 166, in run
allowedServerCNs = self.setupserverCN?)
File "/usr/lib/pymodules/python2.6/Bcfg2/Proxy.py", line 314, in ComponentProxy?
return xmlrpclib.ServerProxy?(newurl, allow_none=True, transport=ssl_trans)
File "/usr/lib/python2.6/xmlrpclib.py", 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 https://kgoetz.selfip.net:6789
A fix has been committed in [d9cd51cc7449902361611a0cef7cd4b71c57f11f] and will be included in 1.2.0pre1