Bug 846016

Summary:	[vdsm] [Setup Host Networks] After changing nics for network, both ifcfg files are left with BRIDGE=<networkName>
Product:	Red Hat Enterprise Linux 6	Reporter:	Muli Salem <msalem>
Component:	vdsm	Assignee:	Dan Kenigsberg <dkenigsb>
Status:	CLOSED DUPLICATE	QA Contact:	Meni Yakove <myakove>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	abaron, bazulay, iheim, lpeer, ykaul
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-07 06:37:19 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:

Description Muli Salem 2012-08-06 14:01:18 UTC

Description of problem:
When changing interfaces for a network, ifcfg file in old interface is left with BRIDGE=<networkName>.

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

How reproducible:
always

Steps to Reproduce:
From WebAdmin:
1. Add host with more than 1 NIC to setup.
2. Add a network which is defined as a vm network.
3. In Setup Host Networks, assign this network to a nic and click OK.
4. In Setup Host Networks, drag the network to another nic and click OK.
  
Actual results:
Both /etc/sysconfig/network-scripts/ifcfg-<originalNicName>
and /etc/sysconfig/network-scripts/ifcfg-<newNicName>
have BRIDGE=<networkName>

Expected results:
The line should be removed from /etc/sysconfig/network-scripts/ifcfg-<originalNicName>

Additional info:
Also need to make sure the bridge that is up is not connected to both nics.

Comment 1 lpeer 2012-08-07 06:37:19 UTC


*** This bug has been marked as a duplicate of bug 845193 ***