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

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 831528

Summary:	3.1 - Allow multiple VLANed network together with on only one non-VLANed bridgeless network on top of NIC/Bond
Product:	Red Hat Enterprise Linux 6	Reporter:	Igor Lvovsky <ilvovsky>
Component:	vdsm	Assignee:	Igor Lvovsky <ilvovsky>
Status:	CLOSED ERRATA	QA Contact:	GenadiC <gcheresh>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	abaron, aburden, bazulay, cpelland, dkenigsb, iheim, jbiddle, lpeer, mavital, sgrinber, yeylon, ykaul
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Networking
Fixed In Version:	vdsm-4.9.6-25.0	Doc Type:	Bug Fix
Doc Text:	Previously, the VDSM was unable to attach several VLANed networks to same NIC/bond interface. This upgrade allows multiple VLANed networks to be attached. In order to ensure network security this feature has been restricted to the following configurations: a single bridged non-VLANed network, or a single bridgeless non-VLANed network plus any amount of bridged/bridgeless VLANed networks.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-04 18:59:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	841513

Description Igor Lvovsky 2012-06-13 08:51:55 UTC

Description of problem:

Allow multiple VLANed network together with on only one non-VLANed on top of NIC/Bond 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Igor Lvovsky 2012-06-13 10:27:06 UTC

http://gerrit.ovirt.org/#/c/5311/

Comment 2 lpeer 2012-06-14 11:00:25 UTC

We should not allow running VMs on the non-VLANed network to avoid security breatch, the network should be bridgeless.

Comment 4 Igor Lvovsky 2012-07-18 10:33:33 UTC

Only following combinations are allowed:
     - single non-VLANed bridged network
     - multiple VLANed networks (bridged/bridgeless) with only one
       non-VLANed bridgeless network

This should be verified for bond and nic interfaces separately.

http://gerrit.ovirt.org/#/c/6384/

Comment 6 GenadiC 2012-08-05 13:01:58 UTC

Verified in SI13 besides the case that its impossible to create combination on VLAN and non_VLAN non_VM network in one step

Comment 9 errata-xmlrpc 2012-12-04 18:59:49 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/RHSA-2012-1508.html