https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OVSDB-438 ovsdb <p>When southbound devices are connected to odl cluster via ha proxy.</p> <p>each client is connected to single odl node.</p> <p>Some times when the connection flap happens, its node goes missing from operational datastore.</p> <p>client connects to only one odl controller via ha proxy</p> <p>1) client disconnects and connects back to same node after some delay<br/> 2) client disconnects and connects back to same node immediately<br/> 3) client disconnects and connects to another node after some delay<br/> 4) client disconnects and connects to another node immediately<br/> 5) client disconnects and never connects back</p> <p>When client disconnects all the odl controllers are trying to cleanup the oper<br/> node.<br/> When client connects the owner odl controller is trying to create the oper node.</p> <p>When the processing of one odl controller which is trying to cleanup the opernode is<br/> delayed , then we end up client node missing in oper topology.</p> OVSDB-438

operational node goes missing upon ovsdb node connection flap when haproxy is enabled

Bug Medium Resolved Done suneelu varma suneelu varma Fri, 15 Dec 2017 07:15:05 +0000 Wed, 23 May 2018 04:38:20 +0000 Wed, 23 May 2018 04:38:20 +0000 Southbound.hw_vtep Southbound.Open_vSwitch 0 1 Relates OVSDB-439 OVSDB-433 OVSDB-434 Development Rank 0|i0391b: