Red Hat Bugzilla – Bug 163248
ifenslave adds interfaces to bond regardless of errors encountered during enslave process
Last modified: 2007-11-30 17:07:19 EST
Description of problem:
The current version of ifenslave adds an interface to a bonded interface
regardless of errors encountered during the enslave process. In particular,
this behavior can be seen when the bond interface MTU cannot be set on a slave
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install 2 nics in a machine
2.set the bond mtu to a value that is unsupported by one of the physical interfaces
3.ifensalve the physical interfaces to the bond.
Errors regarding failure to set MTU will be generated, but interface will still
be enslaved (IFF_SLAVE will be set on the interface).
Slave should not be added to bond when errors are encountered.
The latest version of ifenslave is able to unwind changes that it makes so that
it can return the slave interface to its origional state in the event of an error
Created attachment 116753 [details]
latest version of ifenslave
Which version of ifenslave are they currently using? Cos there's no difference
between to one you've attached and the one we ship in RHEL4. iputils-20020927-18
already include ifenslave 1.1.0.
They're using the ifenslave version from the U1 package, iputils-20020927-16,
which is what shipped with RHEL4-U1 and is the latest available on RHN. It uses
ifenslave.c version 1.0.12, not 1.1.0. Can you confirm that iputils-20020927-18
uses ifenslave 1.1.0 and will be available in U2?
Aha, I haven't realized that -18 version didn't make it to RHEL4 base - strange,
cos the split happened with -18 version. There's no update scheduled for iputils
so far, I'm adding this bug on proposed list but I can't promise it will appear
in U2 as it's the only bugfix in this package.
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.