[Yahoo-eng-team] [Bug 1935888] [NEW] When multiple neutron servers are restarted, the update from neutron MariaDB to ovn North database is triggered, and the neutron server generates contention lock,

Public bug reported: Multiple neutrron server restart, triggering the update of neutron MariaDB to ovn North database. Because acceleration is asynchronous, when a neutron server obtains OVS IDL lock (ovn_ db_ inconsistencies_ After Periodics), but other neutron server can not get the lock,

[Yahoo-eng-team] [Bug 1927293] [NEW] When ACL rules are synchronized, other rules docking with ovn vendors will be deleted by mistake

Public bug reported: If ovn connects with other manufacturers, it will lead to the inconsistency between the ACLS configuration data in MariaDB and the data in the northbound database in ovn. When trying to synchronize ACL rules, it will only synchronize according to the ACLS in neutron, and

[Yahoo-eng-team] [Bug 1896571] Re: When forwarding rules of floating IP port are updated, internal_ Ip_ Address and internal_ port_ ID mismatch

Ths，yulong comments, My neutron Code is not new enough and changes have been found on the new version https://github.com/openstack/neutron/blob/master/neutron/services/portforwarding/pf_plugin.py#L481-#L490 ** Changed in: neutron Status: In Progress => Invalid -- You received this bug

[Yahoo-eng-team] [Bug 1896571] [NEW] When forwarding rules of floating IP port are updated, internal_ Ip_ Address and internal_ port_ ID mismatch

| | qos_policy_id | | | revision_number | 23 | | security_grou

[Yahoo-eng-team] [Bug 1896563] [NEW] Floating IP port forwarding rule update external_ Port, HTTP return code 500 error

Public bug reported: When an existing port forwarding rule is updated on the floating IP, if the external_port field contained in the updated content is the same as that in other port forwarding rule entries under the floating IP, the HTTP return code is 500; The log of the neutron server