[OVSDB-322] Southbound plugin doesn't allow controller initiated re-connection Created: 16/Mar/16 Updated: 30/Oct/17 Resolved: 17/May/16 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Southbound.Open_vSwitch |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Anil Vishnoi | Assignee: | Anil Vishnoi |
| 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: | 5542 |
| Description |
|
Southbound plugin does not allow controller initiated re-connection,if the previous connection was terminated from switch side and not from controller side (through data store). Steps to recreate the issue: (1) Set OVS switch to listen in passive mode Controller won't connect to the switch. Log message shows following log message |
| Comments |
| Comment by Anil Vishnoi [ 16/Mar/16 ] |
|
master : https://git.opendaylight.org/gerrit/#/c/36279/1 |
| Comment by Anil Vishnoi [ 16/Mar/16 ] |
|
When controller initiated connection gets terminate from switch side (because of network outage, switch removed, machine down etc), it does not clear the instance identifier cache. When controller removes the configuration and connects back, it checks if the relevant IID is present in the cache, if it's present it assumes that controller is already connected. Above patches cleans up the cache and that resolves the issue. |
| Comment by Vishal Thapar [ 17/Mar/16 ] |
|
Similar fix is needed for hwvtep too. I've raised a patch using the same bug-id: stable/beryllium: https://git.opendaylight.org/gerrit/#/c/36381/ |