[OVSDB-438] operational node goes missing upon ovsdb node connection flap when haproxy is enabled Created: 15/Dec/17 Updated: 23/May/18 Resolved: 23/May/18 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Southbound.hw_vtep, Southbound.Open_vSwitch |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | suneelu varma | Assignee: | suneelu varma |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
When southbound devices are connected to odl cluster via ha proxy. each client is connected to single odl node. Some times when the connection flap happens, its node goes missing from operational datastore. client connects to only one odl controller via ha proxy 1) client disconnects and connects back to same node after some delay When client disconnects all the odl controllers are trying to cleanup the oper When the processing of one odl controller which is trying to cleanup the opernode is |