Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1524076

Summary: installation and timeout connecting to VDSM daemon
Product: [oVirt] ovirt-hosted-engine-setup Reporter: Hetz Ben Hamo <hetz>
Component: GeneralAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, danken, hetz
Target Milestone: ---   
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: 2017-12-19 17:05:38 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:
Attachments:
Description Flags
Files as requested (in ZIP format) none

Description Hetz Ben Hamo 2017-12-09 23:54:13 UTC 
The following happens to me few days ago and if needed, I'll try to reproduce and add logs to this bug...

Situation: When using oVirt node NG ISO to install on a new machine and trying the install the HE using CLI, sometimes the appliance download is slow (slow as 3-5% downloading each line) and when it finishes downloading the appliance and it tries to continue the installation, it failes with error that it cannot communicate with VDSM daemon.

When it failed, I checked if the VDSM daemon was stopped. It wasn't.

Restarting the HE script with previous answer file (that was generated when the first attempt fails), the installation works without any problem.
Comment 1 Sandro Bonazzola 2017-12-11 07:00:35 UTC 
Can you please provide sos report from the oVirt Node NG host?
We have not enough information for diagnosing the issue.
Comment 2 Hetz Ben Hamo 2017-12-11 07:48:02 UTC 
Sure. How do I generate this report?
Comment 3 Dan Kenigsberg 2017-12-11 12:26:31 UTC 
running `ovirt-log-collector` in the Hosted Engine VM should do the trick, I believe.
Comment 4 Yaniv Kaul 2017-12-11 16:10:35 UTC 
(In reply to Dan Kenigsberg from comment #3)
> running `ovirt-log-collector` in the Hosted Engine VM should do the trick, I
> believe.

I think we need the installation logs. I kinda remember seeing this in the past.
Comment 5 Hetz Ben Hamo 2017-12-11 17:00:43 UTC 
Created attachment 1366206 [details]
Files as requested (in ZIP format)
Comment 6 Hetz Ben Hamo 2017-12-11 17:02:58 UTC 
Files enclosed. I'm keeping the VM, so if other files are required, please tell me. There is no ovirt-log-collector in the NG ISO.
Comment 7 Simone Tiraboschi 2017-12-19 17:05:38 UTC 

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