Bug 833803

Summary:	3.1 - Avoid bond breaking after network detach
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, bazulay, cpelland, danken, iheim, jbiddle, lpeer, sgrinber, yeylon, ykaul
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:	vdsm-4.9.6-18.0	Doc Type:	Enhancement
Doc Text:	Previously, if a network was detached using the VDSM, all bonds in place would also be released. Now, when using VDSM to detach networks, the option is available to either release the bond or leave it in place.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-04 19:00: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-06-20 11:42:07 UTC

Description of problem:

When we detach network defined on top of the bond, bond itself should stay
as is.
Now vdsm break it


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


How reproducible:


Steps to Reproduce:
1. create bond with network on it
2. detach network
3.
  
Actual results:
Network detached and bond released

Expected results:
Network should be detached but bond should stay as is

Additional info:

Comment 1 Igor Lvovsky 2012-06-26 13:22:08 UTC

http://gerrit.ovirt.org/#/c/5711/1
http://gerrit.ovirt.org/#/c/5712/

Comment 3 Igor Lvovsky 2012-06-29 17:58:13 UTC

Yes, it's exactly what we discussed 
now vdsm does exactly what engine ask it.
Only if engine ask to break bond during detach network we will do it.

Comment 6 GenadiC 2012-07-16 06:08:13 UTC

Verified in 3.1 SI10 (vdsm-4.9.6-21.0.el6_3.x86_64)

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