Bug 1273936

Summary: [CI] Increasing again timeouts to avoid false positives on CI jobs
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Simone Tiraboschi <stirabos>
Component: Plugins.GeneralAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED DUPLICATE QA Contact: Ilanit Stein <istein>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.3.0CC: bugs, didi, lveyde, rmartins, sbonazzo, stirabos
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-21 14:34:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Simone Tiraboschi 2015-10-21 14:26:53 UTC
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:

Comment 1 Simone Tiraboschi 2015-10-21 14:34:15 UTC

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