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:
Normal: ServerA is holding VRRP managed address w.x.y.z, ServerB is backup for the address w.x.y.z. 

ServerA is suspended, so that ServerB transitions to master.
ServerA is resumed, now both servers are masters for a little while. Then ServerB goes into standby.

At this point the ARP table still points at ServerB for the w.x.y.z address, but ServerB doesn't answer to this address anymore. This is quite bad.

Version-Release number of selected component (if applicable):


How reproducible:
recover from failed/master to  master/backup

Steps to Reproduce:
1. setup master/backup environment
2. kill master 
3. wait until failover 
4. recover master

Actual results:
arp table is not cleared 

Expected results:
arp table cleared


Additional info:
It is fixed in following mainstream patch.
https://github.com/acassen/keepalived/commit/44a885325d1b825416bab7d2fe07cf8cd6c95ece

Well aware of this. Will be fixed as part of rebase in RHEL6.6 (BZ#1052380).

*** Bug 1110363 has been marked as a duplicate of this bug. ***

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-2014-1510.html