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-286 ovsdb <p>the final result is an ovs instance thinking it's connected to the plugin (e.g. "is_connected: true") but it does not exist in operational.</p> <p>steps to reproduce:</p> <p>1. connect ovs node to plugin (ovs-vsctl set-manager)</p> <p>2. partition node from controller with iptables:<br/> sudo /sbin/iptables -A OUTPUT -p tcp --dport 6640 -j DROP</p> <p>3. clear ip tables so communication is ok again.</p> <p>4. create a bridge via northbound rest api</p> <p>notes:</p> <p>It doesn't appear that the plugin times out the connected node when it<br/> stops hearing from it (between steps 2 and 3). I've let it sit for many<br/> minutes like this and it remains in operational.</p> <p>after step 3, the plugin throws an exception because the node connecting<br/> again "was already registered for ownership"</p> <p>after step 4, the plugin removes the node because it "has no owner, cleaning up the operational data store"</p> <p>full karaf log attached</p> <p>Operating System: All<br/> Platform: All</p> OVSDB-286

ovs node removed from operational after partitioned from network and a config is made

Bug Resolved Done Ananthi Palaniswamy Jamo Luhrsen Tue, 2 Feb 2016 01:59:04 +0000 Tue, 28 Jun 2016 06:35:52 +0000 Tue, 28 Jun 2016 06:35:52 +0000 unspecified Southbound.Open_vSwitch 0 4 <p>Attachment 5178.karaf.log has been added with description: karaf.log</p> <p>Attachment karaf.log-1 has been added with description: another newer log for reference</p> <p>This is still seen in CSIT. There is not any of the "partitioning" happening<br/> either, like I initially wrote. Through the normal course of running suites<br/> this is hit. I attached a recent karaf.log from ovsdb-csit-1node-southbound-all-beryllium.</p> <p>It's reproducible locally as well, just running some of the ovsdb suites<br/> back to back. You can get in a state where everything appears clean, and<br/> then try to connect ovs to southbound and we end up in this bug state.</p> <p>by clean, I mean there is nothing in config or operational store. ovs<br/> is showing not connected. Simply doing vsctl set-manager and ovs shows<br/> that it is connected, then ODL operational does not have it.</p> <p>in karaf.log you can see this message when this happens:</p> <p>2016-04-06 21:23:19,854 | INFO | lt-dispatcher-17 | OvsdbConnectionManager | 173 - org.opendaylight.ovsdb.southbound-impl - 1.2.3.beryllium-daily-v201604020031 | Entity{type='ovsdb', id=/(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[</p> {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=ovsdb:1} <p>]/node/node[</p> {(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)node-id=ovsdb://209.132.179.50:6634} <p>]} has no owner, cleaning up the operational data store</p> <p>Attachment Steps_toreproduce.txt has been added with description: Steps followed to reproduce the bug</p> <p>Hi Jamo,</p> <p>Attached the steps followed , not getting the exception as you have mentioned in attached karaf log. Reproduced the bug used latest Beryllium and attached recent karaf log.</p> <p>Attachment karaf.log has been added with description: Attached recent karaf log</p> <p>Hi Jamo, Looks like this issue is fixed now. I am closing this bug, but if you still see this bug, please re-open it.</p> Development External issue ID 5178 External issue URL Issue Type Rank 0|i021sn: