Description of problem: One of our customers ended up having RHOSP deployment where on of VIPs (used by OVN DB) matched IP address configured on his switch. In customer's case this VIP was allocated from appropriate subnet pool, so at the end of the day this looks like configuration issue. At the same time, we have checks for regular IP addresses and it would be good to implement something similar to check if there are existing hosts with allocated VIP addresses in proper networks before actually setting them. I am not sure if this should be done by deployment framework, or VIP pacemaker resource could do something similar, or different component should be responsible for this. So I have selected openstack-tripleo-heat-templates component for initial triage.
when run_arping=true and pacemaker detects a collision one can find the following in pacemaker.log: Sep 07 05:54:54 IPaddr2(ip-172.17.1.31)[209771]: ERROR: IPv4 address collision 172.17.1.31 [DAD] Sep 07 05:54:54 IPaddr2(ip-172.17.1.31)[209771]: ERROR: Failed to add 172.17.1.31
ExtraConfig: pacemaker::resource::ip::run_arping: true Resource: ip-172.17.3.115 (class=ocf provider=heartbeat type=IPaddr2) Attributes: ip-172.17.3.115-instance_attributes cidr_netmask=32 ip=172.17.3.115 run_arping=true
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 (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577