Description of problem:
The fix for bug #483711 cleans up /sys/class/net/bondX/bonding/arp_ip_target in
When using /etc/modprobe.conf to set the bonding options (and not BONDING_OPTS
in /etc/sysconfig/network-scripts/ifcfg-bond<x>, ie old-style config), then the
interface will not come up after a network restart because the arp_ip_target is
BZ604669 takes care of the same issue on RHEL5.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. set bonding with a /etc/modprobe.d/bonding.conf file.
alias bond0 bonding
options bond0 mode=1 arp_interval=1000 arp_ip_target=192.168.0.1
2. start network service.
# service network start
3. restart network service.
# service network restart
bond0 will never come up because the arp_ip_target is cleared in ifdown
the arp_ip_target should be restored even when specified in modprobe.conf
With repsect to the specific patch, see https://bugzilla.redhat.com/show_bug.cgi?id=604669#c3
Upstream version at 5749d2e9d5795fdaf65b97befd64cf90103d423d.
Need b24d6b8 as well.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
bonding set with a /etc/modprobe.d/bonding.conf file
What happens when the bug presents.
bond0 will never come up after service network restart
the arp_ip_target is restored even when specified in modprobe.conf
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.