data inconsistent in subscribe info in topology module
Bug #1596455 reported by
hujie
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DragonFlow |
Fix Released
|
High
|
hujie |
Bug Description
In current topology implementation, when a new VM is created and the ovs-interface port was notified to topology module, if it could not find the corresponding lport object from DF DB (for example, the db connection breaks down), topology will not invoke the _add_to_
So we need a mechanism to make the subscribe info consistent(for example when the db connection is recovered and established again)
Changed in dragonflow: | |
importance: | Undecided → High |
To post a comment you must log in.
I will add the bug fix implement in my new db consistency patch for local controller