Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 888315

Summary: 3.1.3 Failed to break BOND and attach custom MTU networks while VM is running
Product: Red Hat Enterprise Linux 6 Reporter: Dan Kenigsberg <danken>
Component: vdsmAssignee: Igor Lvovsky <ilvovsky>
Status: CLOSED ERRATA QA Contact: Meni Yakove <myakove>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3CC: abaron, bazulay, cpelland, iheim, lpeer, mavital, myakove, tlavigne, ykaul, zdover
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: vdsm-4.10.2-1.1.el6 Doc Type: Bug Fix
Doc Text:
Previously, the tap device on the bridge was counted as a part of the bond because of incorrect behavior in getNicsVlanAndBondingForNetwork. This meant that it was not possible to break a virtual machine's bond to an attached network while the virtual machine was running, which meant that it was not possible to attach a custom MTU network while the virtual machine was running. getNicsVlanAndBondingForNetwork has been altered so that it no longer counts the tap device on the bridge as part of the bond. It is now possible to break a virtual machine's bond to an attached network while the virtual machine is running, and that makes it possible to attach a custom MTU network while the virtual machine is running.
 Story Points: ---
Clone Of: 875487 Environment:
Last Closed: 2013-02-25 19:07:07 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:
Bug Depends On: 875487    
Bug Blocks: 862559    

Comment 1 Dan Kenigsberg 2012-12-23 10:35:47 UTC 
https://gerrit.eng.lab.tlv.redhat.com/#/c/3797/
Comment 3 Meni Yakove 2013-01-23 07:21:38 UTC 
Verified on vdsm-4.10.2-3.0.el6ev.x86_64.

Get error that network is in use.
Comment 5 errata-xmlrpc 2013-02-25 19:07:07 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/RHBA-2013-0555.html