Bug 1051150

Summary:	RHEV 3.2 hypervisor setup adds ifcfg VLAN attr to NIC parent of rhevm net subint
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Dave Sullivan <dsulliva>
Component:	vdsm	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED ERRATA	QA Contact:	Martin Pavlik <mpavlik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2.0	CC:	acathrow, bazulay, iheim, lbopf, lpeer, mpavlik, myakove, nyechiel, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Red Hat Enterprise Virtualization Hypervisor setup no longer sets VLAN=yes attribute in the parent physical NIC (network interface card) when the Red Hat Enterprise Virtualization Manager network is a VLAN sub-interface.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-09 13:27:29 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:
Bug Blocks:	1078909, 1142926

Description Dave Sullivan 2014-01-09 18:52:18 UTC

Description of problem:

At setup / addition of a hypervisor to RHEV 3.2 RHEV-M, if the rhevm network is a VLAN sub-interface the parent physical NIC will get the VLAN=yes attribute set in its /etc/sysconfig/network-scripts/ ifcfg file.


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

3.2 but expected to be same problem with 3.3


How reproducible:

Seee Description above

parent physical nic should is getting VLAN=yes setting

Actual results:


Expected results:

parent physical nic should not get VLAN=yes setting


Additional info:

Not entirely sure this should be mapped against vdsm

Comment 2 Dan Kenigsberg 2014-02-18 22:49:24 UTC

There has been an old attempt to handle this in http://gerrit.ovirt.org/#/c/7411/

Comment 3 Dan Kenigsberg 2014-02-18 22:53:55 UTC

The spurious VLAN tag is annoying, but I do not see why it merits a 3.3.z-stream.

Comment 4 Dave Sullivan 2014-02-25 18:48:47 UTC

I agree with Dan that 3.4 is good for this one, as customer is aware of it and has a workaround fix.

Comment 6 Martin Pavlik 2014-03-18 16:23:29 UTC

verified with av3

no VLAN=yes for the parent interface

Comment 7 errata-xmlrpc 2014-06-09 13:27:29 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0504.html