On Thu, Aug 21, 2014 at 6:43 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Il 20/08/2014 09:17, Gianluca Cecchi ha scritto:

>
> On Wed, Aug 20, 2014 at 9:06 AM, Gianluca Cecchi <gianluca.cecchi@gmail.com <mailto:gianluca.cecchi@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 <http://0.0.0.0:54321> refused
>
> what to check?

Maybe the vdsmd daemon is not running.
check if it's up with "service vdsmd status". Looks like the vdsmd daemon is not responding

This is in the middle of install itself....

What is the workflow for engine-setup in AIO install?

At the beginning of engine-setup process I have:

[ INFO ] Hardware supports virtualization

Then in configuration preview I have:

Configure VDSM on this host : True

Then I see

[ INFO ] Stage: Transaction setup

[ INFO ] Stopping engine service

[ INFO ] Stopping ovirt-fence-kdump-listener service

[ INFO ] Stopping websocket-proxy service

[ INFO ] Stage: Misc configuration

[ INFO ] Stage: Package installation

[ INFO ] Stage: Misc configuration

[ INFO ] Initializing PostgreSQL

[ INFO ] Creating PostgreSQL 'engine' database

[ INFO ] Configuring PostgreSQL

[ INFO ] Creating/refreshing Engine database schema

[ INFO ] Creating CA

[ INFO ] Configuring WebSocket Proxy

[ INFO ] Generating post install configuration file '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'

[ INFO ] Stage: Transaction commit

[ INFO ] Stage: Closing up

and

[ INFO ] Starting engine service

[ INFO ] Restarting httpd

[ INFO ] Restarting nfs services

[ ERROR ] Failed to execute stage 'Closing up': [Errno 111] Connection refused

[ INFO ] Stage: Clean up

Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140820084635-z4gm0h.log

[ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140820084948-setup.conf'

[ INFO ] Stage: Pre-termination

[ INFO ] Stage: Termination

[ ERROR ] Execution of setup failed

So where is the vdsmd part configuration information?

DO I have to check vdsm logs or host-deploy logs for this kind of problem?

Gianluca