Bug 833803 - 3.1 - Avoid bond breaking after network detach
3.1 - Avoid bond breaking after network detach
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Igor Lvovsky
Depends On:
  Show dependency treegraph
Reported: 2012-06-20 07:42 EDT by Igor Lvovsky
Modified: 2013-02-28 23:54 EST (History)
10 users (show)

See Also:
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:
Last Closed: 2012-12-04 14:00:18 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Igor Lvovsky 2012-06-20 07:42:07 EDT
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
Actual results:
Network detached and bond released

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

Additional info:
Comment 3 Igor Lvovsky 2012-06-29 13:58:13 EDT
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 02:08:13 EDT
Verified in 3.1 SI10 (vdsm-4.9.6-21.0.el6_3.x86_64)
Comment 9 errata-xmlrpc 2012-12-04 14:00:18 EST
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.


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