[Bug 1939723] Re: neutron-ovn-db-sync generates insufficient flow

[nikhil kshirsagar]

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

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1939723

Title:
  neutron-ovn-db-sync generates insufficient flow

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive ussuri series:
  Fix Committed
Status in Ubuntu Cloud Archive victoria series:
  Fix Released
Status in Ubuntu Cloud Archive wallaby series:
  Fix Released
Status in Ubuntu Cloud Archive xena series:
  Fix Released
Status in Ubuntu Cloud Archive yoga series:
  Fix Released
Status in Ubuntu Cloud Archive zed series:
  Fix Released
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Focal:
  Fix Committed

Bug description:
  = Original bug description =

  In OpenStack version Victoria, neutron-ovn-db-sync generates insufficient flow for port no security-group or disable port-security.
  ---> As a result, the port is not connected to the network.

  = Ubuntu SRU details =

  [Impact]
  The neutron-ovn-db-sync tool is used to syncing neutron networks and ports with OVN databases. When the tool is run, ports with port security disabled are incorrectly being added to the drop port group causing all traffic to be dropped by default.

  [Test Case]
  - Create a VM
  - Disable port security
  - Remove NB & SB DB
  - Run command neutron-ovn-db-sync-util to resync from neutron to NB database
  neutron-ovn-db-sync-util --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --ovn-neutron_sync_mode repair
  - Restart ovn-controller
  - VM with port disable security die without the fix

  [Regression Potential]
  This is a simple patch that fixes the logic of an if statement. This has been fixed in the victoria+ Ubuntu package versions since 2022-01-12, and has been fixed in the upstream stable/ussuri branch since 2021-11-11.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1939723/+subscriptions