Bug 510116 - Unable to assign VLAN tags to NICs in firstboot menu
Summary: Unable to assign VLAN tags to NICs in firstboot menu
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Mike Burns
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 509140
TreeView+ depends on / blocked
 
Reported: 2009-07-07 18:36 UTC by Darryl L. Pierce
Modified: 2015-06-22 00:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-18 14:37:47 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Darryl L. Pierce 2009-07-07 18:36:36 UTC
Description of problem:
if the customer's environment requires vlan tags, we can't set them up via the
firstboot menu, only manually using ifcfg scripts and persisting those scripts,
if the customer knows how to. 
vlan setup is there in the GUI, but without the vlan tag, rhev-h will never go
out into the network and will not be attached to rhev-m, so the GUI cannot
control it.

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

How reproducible:
try to install rhev in a VLAN environment, requiring IFs are tagged

Steps to Reproduce:
1. /etc/sysconfig/network-scripts/ifcfg-eth0.555
2.add VLAN=yes
3.add BOOTPROTO=none


Actual results:
In the netowrk configuration menu, VLAN tags aren't mentioned


Expected results:
menu to ask for a vlan tag for the NIC

Additional info:


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