Bug 1242227

Summary:	MTU of VM network should be equal to the MTU of the other networks on the nic
Product:	[oVirt] ovirt-engine	Reporter:	Alona Kaplan <alkaplan>
Component:	General	Assignee:	Yevgeny Zaspitsky <yzaspits>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bugs, danken, ecohen, gklein, lsurette, mburman, rbalakri, yeylon, ylavi
Target Milestone:	ovirt-3.6.0-rc	Flags:	rule-engine: ovirt-3.6.0+ ylavi: Triaged+ ylavi: planning_ack+ rule-engine: devel_ack+ rule-engine: testing_ack+
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:	3.6.0-11	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-04 11:48:35 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:
Bug Depends On:	1193544
Bug Blocks:

Description Alona Kaplan 2015-07-12 12:16:31 UTC

Description of problem:

A recent change introduced the ability to configure VM_NON_VLAN network on the same nic with other VLAN networks.
However, the mtu check cando action wasn't fixed.

All the networks on a nic should have the same mtu as the non-vlan network (no matter if the non-vlan network is vm or non-vm network). Currently this check is enforced only for non-vm networks.

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


How reproducible:


Steps to Reproduce:
I didn't try to reproduce it, just saw the error in the code.

Actual results:


Expected results:


Additional info:

Comment 1 Michael Burman 2015-09-22 06:36:14 UTC

Verified on - 3.6.0-0.16.master.el6 with vdsm-4.17.7-1.el7ev.noarch

Operation Canceled:

Error while executing action: 

silver-vdsa.qa.lab.tlv.redhat.com:
Cannot setup Networks. The following Logical Networks do not have the same MTU value: vlan_6000(6000),
vm_5000(5000).

Comment 2 Sandro Bonazzola 2015-11-04 11:48:35 UTC

oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue.
If problems still persist, please open a new BZ and reference this one.