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):
In dev-scripts environment
1. Check which node holds the VIP
2. run 'virsh shutdown <node> '
Steps to Reproduce:
VIP moved to another node after timeout (3 * interval)
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
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.