Bug 1367458

Summary: hosted-engine --deploy gets stuck on "Waiting for VDSM to reply"
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Alain Penders <alain>
Component: NetworkAssignee: Yedidyah Bar David <didi>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.0.1.4CC: alain, bugs, sbonazzo, stirabos, ylavi
Target Milestone: ---Flags: alain: needinfo-
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
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: 2016-08-24 12:22:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alain Penders 2016-08-16 13:02:02 UTC 
Description of problem:

"hosted-engine --deploy" command gets stuck on Waiting for VDSM to reply.  Waiting half an hour didn't help, neither does restarting vdsmd, etc.   No errors in the vdsm and ovirt-hosted-engine-setup logs.

Version-Release number of selected component (if applicable):

Should be the 4.0.2 release of ovirt .. whatever the latests versions were on Aug 15, 2016.  Running on CentOS 7.2.1511

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Discussed on IRC and someone suggested a DNS issue.  DNS isn't working and was relying on /etc/hosts.  As it turned out, /etc/hosts didn't contain the entry, so FQDN resolution wasn't available at all.   Not sure if I had pointed the FQDN to 127.0.0.1 (as I had done earlier), if this issue would have still happened.    Once I put the FQDN in /etc/hosts, the deploy passed that point.
Comment 1 Yaniv Lavi 2016-08-18 08:09:31 UTC 
Can you attach logs?
Comment 2 Simone Tiraboschi 2016-08-24 12:22:54 UTC 
Without logs I strongly suppose that this is just a duplicate of 1358530.
I'm closing it as duplicate, please reopen if this is not the case.

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