ODL and Neutron can get out of sync due to various conditions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-odl |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The design of the ODL ML2 driver on the southbound side of neutron combined with the design of the Northbound side of ODL interface to neutron is subject to various race conditions that can cause a loss of synchronization.
These race conditions can be triggered in various scenarios. Some of these scenarios have been shared via: https:/
Some cases include:
When the driver attempts to synchronize the two databases especially a full sync other threads may be changing the database and causing corruption.
In a cluster HA scenarios strict ordering of the transactions called out to ODL can't be guaranteed to be in the same order as entered in the neutron database during the pre-commit phase.
It is likely that the scope of the changes necessary to eliminate these race conditions maybe pretty large.
A similar bug:
https:/
was previously entered, but is more limited in scope to a particular case. This bug being broader in scope should ensure that the specific scenario noted is also addressed.
Similar bug /bugs.launchpad .net/networking -odl/+bug/ 1489553
https:/