Bootstrap node keepalived failure when using static IPs and dual stack apiVIPs

[djixyacine]

Version

$ ./openshift-baremetal-install version
./openshift-baremetal-install 4.17.1
built from commit ec752c19172deb76163560366b13d884867e25a6
release image <private_registry>/4.17.1@sha256:e16ac60ac6971e5b6f89c1d818f5ae711c0d63ad6a6a26ffe795c738e8cc4dde
release architecture amd64

Platform:

Baremetal IPI

What happened?

We are currently installing a baremetal IPI dual stack cluster without DHCP. As far as we can tell, there is no way to allocate an IPv4 and an IPv6 static IPs for the bootstrap VM (Ref: https://github.com/openshift/installer/blob/master/data/data/bootstrap/baremetal/files/etc/NetworkManager/system-connections/nmconnection.template). Only one IP from one IP family can be injected via: platform.baremetal.bootstrapExternalStaticIP.

This is a problem for dual stack apiVIPs and ingressVIPs since it prevents keepalived from starting in the boostrap VM, breaking the installation entirely. The reason being identical router ids for both the IPv4 and IPv6 apiVIPs as both of those would have to bind to one single IP (bootstrapExternalStaticIP).

The workaround has been to ssh into the bootstrap node and run: ´ip addr add dev ens3´ then keepalived is able to start and have different router id for each IP.

What you expected to happen?

Have the option to set one IPv4 and IPv6 IPs at the same time so that keepalived in the bootstrap node can host both IPs from both IP families with different router ids.

How to reproduce it (as minimally and precisely as possible)?

Deploy a dualstack IPI baremetal cluster with static IPs and dualstack apiVIPs/ingressVIPs.