Bug 2213871

Summary:	keepalived - vrrp_version 3 results in 'Invalid VRRPv3 checksum'
Product:	Red Hat Enterprise Linux 9	Reporter:	Nathan Coulson <conathan>
Component:	keepalived	Assignee:	Ryan O'Hara <rohara>
Status:	NEW ---	QA Contact:	cluster-qe <cluster-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, cluster-maint, jwboyer, phil.randal
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

Description Nathan Coulson 2023-06-09 16:57:35 UTC

Description of problem:
When using vrrp_version in /etc/keepalived/keepalived.conf, the logs show "Invalid VRRPv3 checksum".  This happened when all servers were EL9, or a mix of EL8/EL9.  (There is no issue when all servers were EL8).

Version-Release number of selected component (if applicable):
AlmaLinux 9.2
Keepalived 2.2.4-6.el9

How reproducible:
Always

Steps to Reproduce:
1. Install keepalived on at least 2 servers
2. global_defs, use vrrp_version 3


Actual results:
"Invalid VRRPv3 checksum" in the logs, as well as servers fighting over the primary server

Expected results:
Server with highest priority being the primary,  without "Invalid VRRPv3 checksum" in logs

Additional info:
It was suggested to me to try compiling with -fno-strict-aliasing, to see if related to https://github.com/acassen/keepalived/issues/2160.  I was unable to reproduce the issue afterwards, so it may be related.
CFLAGS="$RPM_OPT_FLAGS -fno-strict-aliasing"