3139bbcbe6
It is possible for events from the nb/sb to fire before the opposite
db connection is made. These events can call back into driver code
which tries to access the other db before it is connected.
Conflicts:
neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py
neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovsdb_monitor.py
neutron/tests/functional/plugins/ml2/drivers/ovn/mech_driver/ovsdb/test_ovsdb_monitor.py
neutron/tests/unit/plugins/ml2/drivers/ovn/mech_driver/ovsdb/test_ovn_db_sync.py
neutron/tests/unit/plugins/ml2/drivers/ovn/mech_driver/ovsdb/test_ovsdb_monitor.py
neutron/tests/unit/plugins/ml2/drivers/ovn/mech_driver/test_mech_driver.py
Closes-Bug: #1929197
Closes-Bug: #1928794
Closes-Bug: #1929633
Change-Id: If947581b90ced42981c4611c32de8f428a052c69
(cherry picked from commit
|
||
---|---|---|
.. | ||
eventlet | ||
ovn | ||
sanity | ||
upgrade_checks | ||
__init__.py | ||
destroy_patch_ports.py | ||
ipset_cleanup.py | ||
keepalived_state_change.py | ||
linuxbridge_cleanup.py | ||
netns_cleanup.py | ||
ovs_cleanup.py | ||
pd_notify.py | ||
runtime_checks.py | ||
sanity_check.py | ||
status.py |