Bug 1531072

Summary: [HE] The hosted engine deploy got stuck with "Waiting for VM down"
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Kobi Hakimi <khakimi>
Component: GeneralAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED WORKSFORME QA Contact: meital avital <mavital>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 2.2.1CC: bugs, khakimi, nsednev
Target Milestone: ---Keywords: AutomationBlocker, Regression
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
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: 2018-01-08 14:08:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1527394    
Attachments:
Description Flags
hosted engine logs none

Description Kobi Hakimi 2018-01-04 14:10:50 UTC
Created attachment 1376981 [details]
hosted engine logs

Description of problem:
[HE] The hosted engine deploy got stuck with "Waiting for VM down"  

Version-Release number of selected component (if applicable):
rhvm-appliance-4.2-20171207.0.el7.noarch
Red Hat Enterprise Linux Server release 7.5 Beta (Maipo)

How reproducible:
100%

Steps to Reproduce:
1. Reprovision the host to rhel7.5
2. Install the latest rhvm-appliance-4.2-20171207.0.el7.noarch
3. Deploy the hosted engine.

Actual results:
The hosted engine deploy got stuck with "Waiting for VM down"  

Expected results:
Deploy run successfully :)

Additional info:
attached hosted engine logs:
 - agent.log
 - broker.log
 - ovirt-hosted-engine-setup-20180104120611-65za7a.log
 - vdsm.log

This deploy ran on ge-4 over nfs(lynx09.qa.lab.tlv.redhat.com) 

irosenzw start to investigate it

Comment 1 Nikolai Sednev 2018-01-04 14:39:12 UTC
Can you please add ovirt-hosted-engine-setup and ovirt-hosted-engine-ha versions please?

Comment 2 Yaniv Kaul 2018-01-04 16:26:12 UTC
New deployment or vintage deployment?
Is it reproducible?
What was the state of the VM?

Comment 3 Kobi Hakimi 2018-01-08 13:37:39 UTC
sorry but I tried to reproduce it in 3 different environments 
but can't reproduce it even with the same environment which failed in the beginning.

maybe its related to the rhel-7.5 changes

if no one else has this issue maybe we can close this ticket.

Comment 4 Yaniv Kaul 2018-01-08 14:08:20 UTC
(In reply to Kobi Hakimi from comment #3)
> sorry but I tried to reproduce it in 3 different environments 
> but can't reproduce it even with the same environment which failed in the
> beginning.
> 
> maybe its related to the rhel-7.5 changes
> 
> if no one else has this issue maybe we can close this ticket.

Closing - feel free to re-open if it is reproduced!