Comment 21 for bug 1939723

here are all my attempts today to reproduce the issue firstly - https://pastebin.ubuntu.com/p/vGr9RN57PX/

I am not yet sure if I have a successful reproducer before I can test the fix, but I could not ssh into the VM after the last step ,

"$ openstack server ssh testvm1 --private --login ubuntu" did not return, so I need to check if this is the expected behavior of the reproducer. The status however showed active and not failed,

+--------------------------------------+---------+--------+------------------------+-------+----------+
| ID | Name | Status | Networks | Image | Flavor |
+--------------------------------------+---------+--------+------------------------+-------+----------+
| 94e0949a-5da2-4f3a-84ed-4673cf31fc9b | testvm1 | ACTIVE | private=192.168.21.129 | jammy | m1.small |
+--------------------------------------+---------+--------+------------------------+-------+----------+

I have emailed congnt95 and also will check with other openstack experts if these testing steps are correct, and if this is a workable reproducer, I will install the proposed package on the neutron-api node and check if the vm is reachable in that case after the last step of rebooting the ovn-central nodes after repairing the database using

# sudo neutron-ovn-db-sync-util --config-file /etc/neutron/neutron.conf.copy --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --ovn-neutron_sync_mode repair