Bug 1323143 - After a successful host-deploy, vdsm fails to bring up the network
Summary: After a successful host-deploy, vdsm fails to bring up the network
Keywords:
Status: CLOSED DUPLICATE of bug 1322257
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: 4.17.18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Dan Kenigsberg
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-01 11:28 UTC by David Caro
Modified: 2016-06-26 23:51 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-04-01 21:46:22 UTC
oVirt Team: Network
Embargoed:
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)
Engine and vdsm logs of the whole setup (597.40 KB, application/x-gzip)
2016-04-01 11:28 UTC, David Caro
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.