Bug 845193

Summary:	3.1 - Remove BRIDGE from nic/bond config files (ifcfg-*) when bridged network detached
Product:	Red Hat Enterprise Linux 6	Reporter:	Igor Lvovsky <ilvovsky>
Component:	vdsm	Assignee:	Igor Lvovsky <ilvovsky>
Status:	CLOSED ERRATA	QA Contact:	Meni Yakove <myakove>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.4	CC:	abaron, aburden, bazulay, cpelland, iheim, lpeer, msalem, ykaul, zdover
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:	vdsm-4.9.6-32.0	Doc Type:	Bug Fix
Doc Text:	Previously, when you detached a bridged network from a NIC or bond, the BRIDGE line was not removed from the ifcfg-.config files. This meant that the bridge network was effectively still connected to the NIC or bond. An update has been made to VDSM that makes sure that the BRIDGE line is removed from the ifcfg-.config files when a bridged network is detached from a NIC or bond.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-04 19:04:18 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 Igor Lvovsky 2012-08-02 07:57:56 UTC

Description of problem:

When remove bridge from nic/bond the BRIDGE line should be removed fro proper conf file


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


How reproducible:


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


Expected results:


Additional info:

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

*** Bug 846016 has been marked as a duplicate of this bug. ***

Comment 2 Igor Lvovsky 2012-08-30 06:51:02 UTC

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

Comment 4 Meni Yakove 2012-09-05 13:38:43 UTC

Verified on vdsm-4.9.6-32.0.el6_3.x86_64

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