Red Hat Bugzilla – Bug 199706
ifdown does not invoke ifenslave -d on a bonded interface member.
Last modified: 2010-10-22 01:29:54 EDT
/sbin/ifdown does not invoke "/sbin/ifenslave -d" on a bonded interface member.
If we bring down this interface : ifdown eth2, we can't bring it back up by any
This produces a situation where the interface becomes unusable without bouncing
the whole bond. This situation is suitable for enterprise high-reliability
This bug is also present in RHEL3 initscripts (yes, I know it's too late, but I
thought I'd mention it).
The attached patch allows you to :
- remove a slave from an active bonding and being able to retach it to either
the old one (preserving its configuration) or to assign other configuration
making it active (manually).
- detach the slaves from the bonding if we ask to bring down the bonding itself.
Let me know if there's need for more details,
Created attachment 132815 [details]
Patch fixing this problem.
Why check with ip - why not just unilaterally remove the slaves?
Created attachment 132824 [details]
initscript-ifdown2.patch without IP
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Added in CVS, will be in 7.93.26.EL-1 or later.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.