Bug 1296613

Summary: ovirtmgmt bridge is not configured on newly deployed host
Product: [oVirt] ovirt-engine Reporter: Martin Perina <mperina>
Component: Host-DeployAssignee: Dan Kenigsberg <danken>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bugs, mperina
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-11 08:04:49 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 none

Description Martin Perina 2016-01-07 16:34:16 UTC
Created attachment 1112495 [details]
engine and vdsm logs

Description of problem:

When I try to install new host using oVirt UI or REST, ovirtmgmt bridge is not configured during host deploy and although installation finished successfully, host status is changed to NonOperational with error: 

 Host does not comply with cluster networks, following networks are missing on host: 'ovirtmgmt'


Both engine and host uses latest Centos 7, RPM installation behaves the same as dev env.

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

ovirt-engine master
vdsm master

How reproducible:

100%

Steps to Reproduce:
1. Install new host into engine
2.
3.

Actual results:

Bridge ovirtmgt is not configured on host -> host is marked as Non Operational 

Expected results:

Host is configured properly and in status Up after successful install

Additional info:

Comment 1 Yaniv Kaul 2016-01-10 08:26:53 UTC
Dup of bug 1296614 ?

Comment 2 Martin Perina 2016-01-11 08:04:49 UTC
There was an error during submitting the bug, so I didn't know that bug was really created :-(

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