[NETVIRT-222] Interface removal events donot keep the Operational and Config Datastores consistent Created: 28/Oct/16 Updated: 01/Dec/16 Resolved: 01/Dec/16 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Boron |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vivekanandan Narasimhan | Assignee: | Vivekanandan Narasimhan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7055 |
| Description |
|
When Interface removal events are recieved, we process removal of flows for that interface. However, we should make sure state of removals are in sync in both Operational DS and Config DS. The Operational DS submit was missing and so the gap in sync can result in flows not removed correctly on interface removals (or so to say VM removals). |
| Comments |
| Comment by Vivekanandan Narasimhan [ 04/Nov/16 ] |
|
This fix is required for Boron SR2. |