[OVSDB-313] OVSDB HWVtep Southbound doesn't retry connection Created: 09/Mar/16 Updated: 30/Oct/17 Resolved: 27/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: | 5479 |
| Description |
|
For active connections, controller is the client and should retry connecting when connection is lost. |
| Comments |
| Comment by Vishal Thapar [ 10/Mar/16 ] |
|
|
| Comment by Sam Hague [ 16/May/16 ] |
|
Vishal, was this one fixed? 5221 was resolved and I thought you added something similar but I can't find it. Thanks, Sam |
| Comment by Vishal Thapar [ 17/May/16 ] |
|
At the time Anil recommended waiting for full reconciliation to come in, but I think we can go ahead. I'll prepare a patchset for this. I've had some vendors testing hwvtep running into similar issue. Just need to sure no impact on l2gw as they were handling reconciliation in application code for not. |
| Comment by Anil Vishnoi [ 17/May/16 ] |
|
Hi Vishal, Even if application want to do connection reconciliation, they can still do with the existing connection reconciliation we implemented in the southbound plugin. Because the only way application can do reconciliation is by removing the connection from data store and then again pushing the connection data. So the moment they will remove the config data from data store, existing connection reconciliation will be stopped anyways. |
| Comment by Vishal Thapar [ 27/May/16 ] |
|
stable/be: https://git.opendaylight.org/gerrit/#/c/39415/ |