Bug 1086032

Summary: If another network has the "required" flag a new host will fail and timeout
Product: [Retired] oVirt Reporter: Andrew Lau <andrew>
Component: ovirt-hosted-engine-setupAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: high    
Version: 3.4CC: bazulay, bugs, didi, gklein, iheim, lveyde, rbalakri, sbonazzo, s.kieske, stevep, stirabos, yeylon
Target Milestone: ---   
Target Release: 3.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: ovirt-3.5.1_rc1 Doc Type: Bug Fix
Doc Text:
Cause: An additional required network has been added after deploying the first host. Consequence: hosted-engine-setup fails trying to deploy an additional host Fix: Adding the host in a non-operational status. Printing a hint for the user that needs to configure network bindings for that host.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-21 16:04:14 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:
Bug Depends On: 1158418    
Bug Blocks: 1192937    
Attachments:
Description Flags
ovirt-hosted-engine-setup
none
vdsm
none
supervdsm
none
connectivity
none
host-deploy_from_hosted_engine
none
host-deploy_from_webgui
none
engine none

Description Andrew Lau 2014-04-10 00:35:06 UTC 
Description of problem:
When adding a new host to the hosted-engine setup, if there is another network in the cluster with the required flag - which I believe is default for any new networks required.

The new host will stay in and eventually time out. This is because the engine has come up within the engine as non-operational as it doesn't meet the cluster's network requirements. (ie. a required network isn't configured on the host)
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] Still waiting for VDSM host to become operational...
[ INFO  ] Still waiting for VDSM host to become operational...

Logging into the engine and assigning the correct networks will let the host come up as operational and succeed the install.

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


How reproducible:
Always

Steps to Reproduce:
1. Install first host
2. Configure a new network in the Default cluster
3. Attempt to bring up a second host

Actual results:
Will timeout

Expected results:
Should let the host be successfully installed and let the user add the networks later. Possibly have it join the cluster in maintenance mode to avoid the issue?

Additional info:
Comment 1 Simone Tiraboschi 2014-10-28 16:00:52 UTC 
Reproduced, I'm attaching the relevant log files as a reference for further investigation.
Comment 2 Simone Tiraboschi 2014-10-28 16:05:01 UTC 
Created attachment 951442 [details]
ovirt-hosted-engine-setup

ovirt-hosted-engine-setup
Comment 3 Simone Tiraboschi 2014-10-28 16:09:34 UTC 
Created attachment 951444 [details]
vdsm

vdsm
Comment 4 Simone Tiraboschi 2014-10-28 16:10:29 UTC 
Created attachment 951445 [details]
supervdsm

supervdsm
Comment 5 Simone Tiraboschi 2014-10-28 16:11:25 UTC 
Created attachment 951447 [details]
connectivity

connectivity
Comment 6 Simone Tiraboschi 2014-10-28 16:45:19 UTC 
It's failing also trying to add the same host from the oVirt web admin gui.
Comment 7 Simone Tiraboschi 2014-10-28 16:46:33 UTC 
Created attachment 951451 [details]
host-deploy_from_hosted_engine

host-deploy
Firt run: from hosted-engine
Comment 8 Simone Tiraboschi 2014-10-28 16:47:31 UTC 
Created attachment 951453 [details]
host-deploy_from_webgui

host-deploy
second run: from oVirt web admin gui
Comment 9 Simone Tiraboschi 2014-10-28 16:51:08 UTC 
Created attachment 951454 [details]
engine

engine
Comment 10 Sandro Bonazzola 2015-01-15 14:36:08 UTC 
This is an automated message: 
This bug should be fixed in oVirt 3.5.1 RC1, moving to QA
Comment 11 Sandro Bonazzola 2015-01-21 16:04:14 UTC 
oVirt 3.5.1 has been released. If problems still persist, please make note of it in this bug report.