[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:
Relates
relates to OVSDB-439 Stale connection check is failing and... Resolved
relates to OVSDB-433 OVSDB entity... node-id=ovsdb://uuid/... Resolved
relates to OVSDB-434 br-int not created after failing over... Resolved

 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
2) client disconnects and connects back to same node immediately
3) client disconnects and connects to another node after some delay
4) client disconnects and connects to another node immediately
5) client disconnects and never connects back

When client disconnects all the odl controllers are trying to cleanup the oper
node.
When client connects the owner odl controller is trying to create the oper node.

When the processing of one odl controller which is trying to cleanup the opernode is
delayed , then we end up client node missing in oper topology.


Generated at Wed Feb 07 20:36:24 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.