Bug 1296613 - ovirtmgmt bridge is not configured on newly deployed host
Summary: ovirtmgmt bridge is not configured on newly deployed host
Keywords:
Status: CLOSED DUPLICATE of bug 1296614
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Host-Deploy
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan Kenigsberg
QA Contact: Pavel Stehlik
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-07 16:34 UTC by Martin Perina
Modified: 2016-02-10 19:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-11 08:04:49 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 (342.41 KB, application/x-gzip)
2016-01-07 16:34 UTC, Martin Perina
no flags Details

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


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