Port group not being available in NB DB during ACL sync
is bit of a corner case but possible during the ML2/OVS
to ML2/OVN migration sync. It can also happen in ML2/OVN
only enviroment. See my detailed description of both
scenarios in the linked Bug.
The easiest fix is to just retry ALL port groups sync
one more time if ACL sync cant find a port group row. This
additional resync is really quick.
Closes-Bug: #2008943
Change-Id: Iac1472f7f896ea434deacb6d236ab469f4f6ed56
(cherry picked from commit 33cf2cdc83a8cee9ee075eb371f779c3d356cf48)
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/890118 /opendev. org/openstack/ neutron/ commit/ da9401aa7455a88 f65953efedb9e0c e797674445
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/victoria
commit da9401aa7455a88 f65953efedb9e0c e797674445
Author: Miro Tomaska <email address hidden>
Date: Wed Mar 1 16:32:50 2023 -0600
Fix ACL sync when default sg group is created
Port group not being available in NB DB during ACL sync
is bit of a corner case but possible during the ML2/OVS
to ML2/OVN migration sync. It can also happen in ML2/OVN
only enviroment. See my detailed description of both
scenarios in the linked Bug.
The easiest fix is to just retry ALL port groups sync
one more time if ACL sync cant find a port group row. This
additional resync is really quick.
Closes-Bug: #2008943 434deacb6d236ab 469f4f6ed56 9ee075eb371f779 c3d356cf48)
Change-Id: Iac1472f7f896ea
(cherry picked from commit 33cf2cdc83a8cee