Bug 1920670

Summary: [IPI baremetal] Keepalived - priority 0 advertisement message not being sent when the container is Sigtermed
Product: OpenShift Container Platform Reporter: Yossi Boaron <yboaron>
Component: Machine Config OperatorAssignee: Yossi Boaron <yboaron>
Status: CLOSED ERRATA QA Contact: Rei <rhalle>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.7CC: bperkins
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: When Keepalived container that holds VIP being SIGTERMed no VRRP proactive message (priority 0 message) is sent Consequence: The VIP migrated to another after VRRP RX timeout Fix: When Keepalived container holds VIP being SIGTERMed a priority 0 VRRP advertisement message is sent. Result: Faster VIP migration in case Keepalived container that holds VIP being SIGTERMed
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-16 18:32: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:

Description Yossi Boaron 2021-01-26 20:33:24 UTC
Description of problem:

When Keepalived container that holds VIP being SIGTERMed (for example , as a result of 'virsh shutdown <node>' command in a virtual environment ) that should trigger a  priority 0 advertisement message  to allow faster VIP migration.

Running  'virsh shutdown <node>' command on a node holding VIP didn't trigger  VRRP priority 0 advertisement message

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

How reproducible:

In dev-scripts environment
1. Check which node holds the VIP
2. run 'virsh shutdown <node> '

Steps to Reproduce:

See above

Actual results:
VIP moved to another node after timeout (3 * interval) 

Expected results:

1. Keepalived in shutdown node should send VRRP priority 0 advertisement message
2. Keepalived in one of the remaining master nodes should hold the VIP as soon as he receives the VRRP priority 0 message

Additional info:

Comment 7 errata-xmlrpc 2021-08-16 18:32: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 (OpenShift Container Platform 4.8.5 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.