Created attachment 1024142 [details] /var/log/ from the host Description of problem: Tried to deploy hosted engine over Gluster. Got to the phase when DB health check completed and the hosted-engine installation waited for VDSM to become operational. In this phase the deployment got stuck. Version-Release number of selected component (if applicable): ovirt-3.6.0-1 ovirt-hosted-engine-setup-1.3.0-0.0.master.20150401110307.git9665976.el7.noarch How reproducible: Always Steps to Reproduce: 1. - Created a new volume in the Gluster server: gluster volume create elad3 replica 3 transport tcp 10.35.160.6:/export/elad3 10.35.160.202:/home/elad/1 10.35.160.203:/home/elad/1 force - Changed owner-gid and owner-uid to vdsm:kvm: gluster volume set elad3 owner-uid 36 gluster volume set elad3 owner-uid 36 - Started the volume: gluster volume start elad3 2. Executed hosted-engine --deploy, picked glusterfs and gave it the path of the volume 3. Installed RHEL6.6 on the VM and executed engine-setup Actual results: After DB health check completed, the installation got stuck with the following: [ INFO ] Waiting for the host to become operational in the engine. This may take several minutes... [ INFO ] Still waiting for VDSM host to become operational... I got this error in the setup log: 20**FILTERED**5-05-**FILTERED** 09:00:2**FILTERED** DEBUG otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._wait_host_ready:**FILTERED**89 VDSM host in state 20**FILTERED**5-05-**FILTERED** 09:02:29 DEBUG otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._wait_host_ready:**FILTERED**83 Error fetching host state: [ERROR]::oVirt API connection failure, (7, 'Failed connect to elad-he.qa.lab.tlv.redhat.com:443; Connection timed out') Expected results: Hosted-engine deployment over Gluster should end successfully. Additional info: /var/log/ from the host
vdsm logs ends at 2015-05-11 08:21:07 while above logs are from 09:02:29. at such time the setup logs: 20**FILTERED**5-05-**FILTERED** 08:2**FILTERED**:05 DEBUG otopi.plugins.ovirt_hosted_engine_setup.engine.add_host add_host._wait_host_ready:**FILTERED**89 VDSM host in installing state vdsm has been stopped by ovirt-host-deploy, executed by ovirt-engine, and it has not been restarted. I need the host-deploy logs and/or the engine logs i order to understand why vdsm has not been restarted.
See possible workarounds in the duplicate bz. *** This bug has been marked as a duplicate of bug 1201355 ***
Closed as duplicate since it seems the same issue described in bug #1201355. When vdsmd service is stopped, it kills glusterfs process causing the storage domain to disappear.
Engine VM moves to Paused so it does seems like the issue reported in bug #1201355