Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1075956

Summary: RHEVM sets defroute=yes, if ovirtmgmt network is created
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Pavlik <mpavlik>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED WONTFIX QA Contact: Martin Pavlik <mpavlik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: amuller, bazulay, gklein, iheim, lpeer, myakove, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.4.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-18 00:33:10 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
log_collector none

Description Martin Pavlik 2014-03-13 09:27:47 UTC
Created attachment 873879 [details]
log_collector

Description of problem:
If user creates ovirtmgmt network in RHEVM (which already has rhevm management network)

ovirtmgmt bridge will get defroute=yes

so host will have 2 bridges (rhevm and ovirtmgmt) with defroute=yes which is unwanted

[root@dell-r210ii-08 ~]# cat /etc/sysconfig/network-scripts/ifcfg-{rhevm,ovirtmgmt}
# Generated by VDSM version 4.14.5-0.el6
DEVICE=rhevm
ONBOOT=yes
TYPE=Bridge
DELAY=0
IPADDR=10.34.66.81
NETMASK=255.255.255.0
GATEWAY=10.34.66.254
BOOTPROTO=none
DEFROUTE=yes
NM_CONTROLLED=no
STP=no

# Generated by VDSM version 4.14.5-0.el6
DEVICE=ovirtmgmt
ONBOOT=yes
TYPE=Bridge
DELAY=0
BOOTPROTO=dhcp
DEFROUTE=yes
NM_CONTROLLED=no
STP=no

it should be taken into account wether we have host in oVirt or in RHEVM and the other name should be ignored.


Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.4.0-0.3.master.el6ev 
vdsm-4.14.5-0.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. have working host in RHEVM
2. create network called ovirtmgmt and assign it to host via SetupNetworks

Actual results:
2 bridges with defroute=yes

Expected results:
only 1 bridge with defroute=yes

Additional info:

Comment 1 Dan Kenigsberg 2014-03-18 00:33:10 UTC
The reported issue is true, but it applies to a very limited hand-crafted case.

If Engine is using clusterLevel >= 3.4, defaultRoute is explicitly sent, set to True for a single bridge, and the bridge name never gets into play.

For lower cluster levels, I hereby document that RHEV users should not define an "ovirtmgmt" network, and that oVirt users should not define a "rhevm" network.

It is possible for the code to take into account whether it's rhev or ovirt, but these d/s-u/s differences is what triggered the RHS bug 1015009, and I'd like to avoid them.