Ovn database master is not copied to the first leapped node which can end up with loss of data about changes that happens during first 1/3rd of controlplane upgrade.
Confirmed. Steps to reproduce: 1) System upgrade controller-0 but don't continue with upgrade. 2) Spawn few vms and start pinging them - this creates records on ctrl1 and ctrl2 3) Continue with upgrade where ctrl1 and ctrl2 are shut off and ctrl0 deploys 4) During deployment when ovndb* starts on ctrl0 the ping starts to fail. I verified that both ctrl1 and ctrl2 ovnsb/nb dbs can be copied and resolve the issue.
*** Bug 2028164 has been marked as a duplicate of this bug. ***
Patch is part of 16.2-trunk-patches.
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 16.2.3 (Train)), 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/RHBA-2022:4793