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.

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:

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.
    
    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

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