[OVSDB-333] Hwvtep tunnel updates and deletes sporadically fail to reflect in Operational DataStore Created: 19/Apr/16 Updated: 30/Oct/17 Resolved: 20/May/16 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Southbound.hw_vtep |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vishal Thapar | Assignee: | Vishal Thapar |
| 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: | 5764 |
| Description |
|
When tunnels are updated or deleted from an HWVTEP device, sometime those changes are not reflected correctly in operational DS. This is most commonly seen with last tunnel to be added on the device. Reason for this is that currently Tunnel table updates are handled by PhysicalSwitchUpdateCommand. So any tunnel updates not accompanied by physicalSwitch updates are lost. This is a limitation of the existing design as physical switch and local/remote locator information is needed to update tunnels in OperationalDS and if it doesn't come in an update from switch there is no way to update/delete tunnels. This impacts tunnel deletion and monitoring the most. |
| Comments |
| Comment by Vishal Thapar [ 19/Apr/16 ] |
|
https://git.opendaylight.org/gerrit/#/c/36846/ adds means to retain certain table updates received in a prior transaction. By leveraging HwvtepDeviceInfo it is now possible to separate out tunnel update/delete into its own command pattern which can work independent of PhysicalSwitchUpdateCommand.java |