Bug 1077201

Summary:	keepalived not sending gratious arp after master/master
Product:	Red Hat Enterprise Linux 6	Reporter:	Lukas Herbolt <lherbolt>
Component:	keepalived	Assignee:	Ryan O'Hara <rohara>
Status:	CLOSED ERRATA	QA Contact:	Brandon Perkins <bperkins>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	cluster-maint, myllynen, roberto.cazzato
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	keepalived-1.2.13-1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-14 07:12:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1052380
Bug Blocks:

Description Lukas Herbolt 2014-03-17 12:59:34 UTC

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

Comment 2 Ryan O'Hara 2014-03-17 16:09:50 UTC

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

Comment 11 Ryan O'Hara 2014-06-17 15:48:48 UTC

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

Comment 14 errata-xmlrpc 2014-10-14 07:12:11 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-2014-1510.html