RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 833803 - 3.1 - Avoid bond breaking after network detach
Summary: 3.1 - Avoid bond breaking after network detach
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Igor Lvovsky
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-20 11:42 UTC by Igor Lvovsky
Modified: 2022-07-09 05:36 UTC (History)
10 users (show)

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.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:00:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1508 0 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 23:48:05 UTC

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
Note You need to log in before you can comment on or make changes to this bug.