Bug 1413373

Summary: [RHVH] Add host is failing on timeout in step 'starting vdsmd'
Product: Red Hat Enterprise Virtualization Manager Reporter: Nelly Credi <ncredi>
Component: ovirt-host-deployAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.6.10CC: bazulay, dougsland, gklein, lsurette, ncredi, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-15 14:04:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
host deploy log none

Description Nelly Credi 2017-01-15 13:36:45 UTC 
Created attachment 1240939 [details]
host deploy log

Description of problem:
Add host is failing on timeout in step 'starting vdsmd'

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Hypervisor release 7.3 (20170110.1.el7ev)
vdsm-4.17.37-1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. provision host with the latest rhvh
2. try adding it to an engine
3.

Actual results:
Failed to install Host host_mixed_1. Processing stopped due to timeout.

Expected results:
host should get installed (vdsmd service should be started)

Additional info:
[root@lynx18 ~]# systemctl status vdsmd
● vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled)
   Active: inactive (dead)

when trying to manually start the service 
it gets stuck
Comment 1 Yaniv Kaul 2017-01-15 13:42:37 UTC 
Just to confirm - Engine is also 3.6.x?
Comment 2 Nelly Credi 2017-01-15 13:45:09 UTC 
of course
its 3.6.10 btw, but there is no such version in bugzilla, so i chose 3.6.9
Comment 3 Nelly Credi 2017-01-15 14:04:34 UTC 
looks like there is already a bug open about this issue

*** This bug has been marked as a duplicate of bug 1412619 ***