Description of problem: Starting VM and setting its console ticket are async operations. Hosted-engine-setup is doing that via VDSM and then is polling to check the result till an explicit exit status (success/failure) or a timeout to avoid getting stuck indefinitely. We are seeing false positives on CI jobs (which run on an overloaded environment which is by far slower than a real environment) due to that timeout as for http://jenkins-ci.eng.lab.tlv.redhat.com/job/hosted_engine_3.6_el7_staticip_nfs3_install_on_7.1/126 So let's increase its value. Version-Release number of selected component (if applicable): hosted-engine-setup 1.3 How reproducible: seldom, you must it the timeout on a really overloaded system. Never seen on real deployiment Steps to Reproduce: 1. launch hosted-engine --deploy 2. 3. Actual results: It can fail with 'The VM is not powering up: please check VDSM logs' while the engine VM simply started a few seconds after that Expected results: It should wait a bit more Additional info:
*** Bug 1273936 has been marked as a duplicate of this bug. ***
Verified on ovirt-hosted-engine-setup-1.3.1-1.el7ev.noarch according to http://jenkins-ci.eng.lab.tlv.redhat.com/job/hosted_engine_3.6_el7_staticip_nfs3_install_on_7.1
According to verification status and target milestone this issue should be fixed in oVirt 3.6.1. Closing current release.