Bug 1323143

Summary: After a successful host-deploy, vdsm fails to bring up the network
Product: [oVirt] vdsm Reporter: David Caro <dcaroest>
Component: GeneralAssignee: Dan Kenigsberg <danken>
Status: CLOSED DUPLICATE QA Contact: Meni Yakove <myakove>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.17.18CC: bugs, eedri
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-01 21:46:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Engine and vdsm logs of the whole setup none

Description David Caro 2016-04-01 11:28:12 UTC 
Created attachment 1142513 [details]
Engine and vdsm logs of the whole setup

Description of problem:
After successfully passing the host-deploy, vdsm fails to bring up the ovirtmgmt interface and thus the host fails to be activated.


Version-Release number of selected component (if applicable):
I'm using latest master snapshot:

vdsm-4.17.999-867.gitc0a086f.el7.centos.noarch


How reproducible:
I'm getting it quite often when trying to run the ovirt-system-tests for the master branch, you can just try to run them yourself using the patch 
   https://gerrit.ovirt.org/#/c/55425/

Steps to Reproduce:
1.Create a clean env with one engine, one nfs storage, one iscsi storage and two hosts
2.Create a dc on the engine with nfs storage, and add both hosts
3.

Actual results:
Most of the time one of the hosts fails to activate due to ovirtmgmt interface missing

Expected results:
Hosts get activated correctly

Additional info:
I've attached the logs of the vms, I can also provide an env where that happens on demand.
Comment 1 Yaniv Kaul 2016-04-01 21:12:12 UTC 
Dup of bug 1322257 ?
Comment 2 David Caro 2016-04-01 21:46:22 UTC 
Yep, looks the same. As I was tild to open a new bug, I did not search for already open ones.

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