Description of problem: Seen this sometimes via our nightly OSP16 job. http://10.19.227.133:8080/job/osp16_nightly_new/27/ Basically the controller replacement, succeeds but the tempest afterwards fail on networking problems. The reason is that the OVN-DBS VIP is in Stopped state. It is in stopped state due to a ban on a node. Likely a leftover from our minor update process where we do ban/unban VIPs to minimize downtime: [root@controller-1 ~]# pcs constraint ref ip-172.17.1.44 Resource: ip-172.17.1.44 colocation-ip-172.17.1.44-ovn-dbs-bundle-INFINITY location-ip-172.17.1.44 cli-ban-ip-172.17.1.44-on-controller-2 order-ovn-dbs-bundle-ip-172.17.1.44-Optional The controller-2 ban is what is problematic. If ovn-dbs runs as Master on controller-2 then the VIP will just not start.
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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement 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. https://access.redhat.com/errata/RHEA-2021:3483