Description of problem:
In case two clusters ended up by chance on the same Ingress virtual router id, there would be membership issues due to the fact that the password is static, in contrast with the other two VIPs, which have it include the cluster name.
Version-Release number of selected component (if applicable): 4.4 ane 4.3
How reproducible: To have the issue you need to deploy two clusters in the same multicast domain in which:
* fletcher8(CLUSTER_A_NAME-vip) = x = fletcher8(CLUSTER_B_NAME)
Steps to Reproduce:
1. Find names that collide under fletcher8
2. Deploy both clusters with the names as above
2. Look at Ingress VIP membership status in keepalived logs (crictl keepalived logs)
Nodes from both clusters are seen as belonging to a single virtual router
Keepalived wrong password messages.
In order to simplify the reproduction, one can just check that the keepalived configuration does not change even if you deploy with different cluster names.
in process of deploying OCP 4.5, hope to get it today
Verified on 4.5.0-0.nightly-2020-03-18-115438
[core@master-0 ~]$ cat /etc/keepalived/keepalived.conf | grep auth_pass
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.