Bug 1367458 - hosted-engine --deploy gets stuck on "Waiting for VDSM to reply"
Summary: hosted-engine --deploy gets stuck on "Waiting for VDSM to reply"
Keywords:
Status: CLOSED DUPLICATE of bug 1358530
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: Network
Version: 2.0.1.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Yedidyah Bar David
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-16 13:02 UTC by Alain Penders
Modified: 2020-07-30 02:29 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-08-24 12:22:54 UTC
oVirt Team: Integration
Embargoed:
alain: needinfo-
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.