Bug 846004

Summary: IP disappears from the NON_VM Network on the NIC, when adding additional VLAN Network to the same NIC
Product: Red Hat Enterprise Linux 6 Reporter: GenadiC <gcheresh>
Component: vdsmAssignee: Igor Lvovsky <ilvovsky>
Status: CLOSED ERRATA QA Contact: GenadiC <gcheresh>
Severity: high Docs Contact:
Priority: high    
Version: 6.3CC: abaron, bazulay, cpelland, iheim, ilvovsky, lpeer, ykaul, zdover
Target Milestone: rcKeywords: Regression, TestBlocker
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: vdsm-4.9.6-31.0 Doc Type: Bug Fix
Doc Text:
Previously, adding a second VLAN to a NIC caused the IP to disappear from the NON_VM network on the NIC. The IP of the NON_VM Network is now preserved when you add a second VLAN to a NIC.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 19:04:38 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:
Attachments:
Description Flags
vdsm log none

Description GenadiC 2012-08-06 13:05:42 UTC
Created attachment 602511 [details]
vdsm log

Description of problem:
When you configure Non VM network on the NIC of the host with static IP and then add VLAN Network to the same NIC on the VM, the static IP of the NON VM network becomes None

How reproducible:
Always

Steps to Reproduce:
1. Add NON_VM Network to the NIC1 of the host and configure static IP for it
2. Add another VLAN Network to the same NIC
3.
  
Actual results:
Static IP of the Non_VM Network disappears from NIC and becomes None

Expected results:
IP of NON_VM Network should be preserved

Additional info:

Comment 2 Igor Lvovsky 2012-08-16 11:33:03 UTC
Please verify it for NIC and BOND interfaces.

http://gerrit.ovirt.org/#/c/7259/1

Comment 4 GenadiC 2012-09-02 11:21:06 UTC
Verified in SI16

Comment 7 errata-xmlrpc 2012-12-04 19:04:38 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