Bug 675079

Summary: Specifying bonding arp_ip_target options in modprobe.conf can prevent restarting network
Product: Red Hat Enterprise Linux 6 Reporter: Takuma Umeya <tumeya>
Component: initscriptsAssignee: initscripts Maintenance Team <initscripts-maint-list>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: asersen, azelinka, mfuruta, notting, plautrba
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: initscripts-9.03.24-1.el6 Doc Type: Bug Fix
Doc Text:
Cause bonding set with a /etc/modprobe.d/bonding.conf file Consequence What happens when the bug presents. bond0 will never come up after service network restart Result the arp_ip_target is restored even when specified in modprobe.conf
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 18:09:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 658636, 697582    

Description Takuma Umeya 2011-02-04 08:48:48 UTC
Description of problem:
The fix for bug #483711 cleans up /sys/class/net/bondX/bonding/arp_ip_target in
ifdown.
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
not restored.
BZ604669 takes care of the same issue on RHEL5. 

Version-Release number of selected component (if applicable):
initscripts-9.03.17-1.el6

How reproducible:
Always

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
  
Actual results:
bond0 will never come up because the  arp_ip_target is cleared in ifdown

Expected results:
the arp_ip_target should be restored even when specified in modprobe.conf

Additional info:

Comment 2 Bill Nottingham 2011-02-04 15:47:06 UTC
With repsect to the specific patch, see https://bugzilla.redhat.com/show_bug.cgi?id=604669#c3

Comment 4 Bill Nottingham 2011-04-12 13:02:32 UTC
Upstream version at 5749d2e9d5795fdaf65b97befd64cf90103d423d.

Comment 5 Bill Nottingham 2011-04-12 13:47:15 UTC
Need b24d6b8 as well.

Comment 9 Petr Lautrbach 2011-10-17 11:15:06 UTC
    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.
    
    New Contents:
Cause
    bonding set with a /etc/modprobe.d/bonding.conf file

Consequence
    What happens when the bug presents.
    bond0 will never come up after service network restart

Result
    the arp_ip_target is restored even when specified in modprobe.conf

Comment 13 errata-xmlrpc 2011-12-06 18:09:08 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-2011-1528.html