On Wed, Aug 20, 2014 at 9:06 AM, Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
result = vdscli.connect().getVdsCapabilities()
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request
self.send_content(h, request_body)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content
connection.endheaders()
File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders
self._send_output()
File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output
self.send(msg)
File "/usr/lib64/python2.6/httplib.py", line 739, in send
self.connect()
File "/usr/lib64/python2.6/site-packages/vdsm/sslutils.py", line 181, in
connect
sock = socket.create_connection((self.host, self.port), self.timeout)
File "/usr/lib64/python2.6/socket.py", line 567, in create_connection
raise error, msg
error: [Errno 111] Connection refused
2014-08-20 08:49:48 ERROR otopi.context context._executeMethod:161 Failed
to execute stage 'Closing up': [Errno 111] Connection refused
Sorry, rereading better, it seems not an nfs problem but with getting host
capabilities...
Probably it should be better to put an echo in setup to confirm nfs part
has finished and that we are in another part of setup...
The server is a kvm guest on Fedora 20 system
Indeed when running manually I get
[root@ovirtita host-deploy]# vdsClient -s 0 getVdsCaps
Connection to 0.0.0.0:54321 refused
what to check?
[root@ovirtita host-deploy]# lsmod|grep kvm
kvm_intel 54317 0
kvm 333734 1 kvm_intel
Thanks,
Gianluca