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/OPNFLWPLUG-704 OpenFlowPlugin <p>I'm using this build: <a href="https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.4.3-SNAPSHOT/distribution-karaf-0.4.3-20160530.142832-194.zip" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.4.3-SNAPSHOT/distribution-karaf-0.4.3-20160530.142832-194.zip</a></p> <p>And I'm running ODL in 3-node cluster. </p> <p>After connecting mininet to cluster (sudo mn --controller 'remote,ip=10.25.2.14,port=6633' --controller 'remote,ip=10.25.2.13,port=6633' --controller 'remote,ip=10.25.2.12,port=6633' --topo tree,3 --switch ovsk,protocols=OpenFlow13) operational inventory DS shows data correctly. But after quitting (and cleaning up) mininet, data are still present in operational inventory datastore.</p> <p>Operating System: Linux<br/> Platform: PC</p> OPNFLWPLUG-704

Operational Inventory data persists in datastore after network is disconnected

Bug Resolved Done Juraj Sebin Juraj Sebin Wed, 1 Jun 2016 07:01:59 +0000 Mon, 27 Sep 2021 09:01:49 +0000 Thu, 21 Jul 2016 07:34:19 +0000 General 0 4 <p>Attachment karaf.log.12 node 1 has been added with description: karaf log</p> <p>Attachment karaf.log.13 has been added with description: karaf log node 2</p> <p>Attachment karaf.log.14 has been added with description: karaf log node 3</p> <p>Hi Juraj,</p> <p>Are you using having switches in OFHA (same switches connected to multiple controller nodes ) and which version of the ofplugin are you using Li-plugin ?</p> <p>Hi Shuva,</p> <p>Yes, I believe that with mininet command I posted, every switch is connected to all cluster nodes.</p> <p>Regarding the ofplugin version, it should be lithium version. This is list of installed features:<br/> odl-restconf-noauth,odl-mdsal-clustering,odl-openflowplugin-flow-services-rest-li,feature-jolokia,odl-openflowplugin-app-table-miss-enforcer</p> <p>I was able to reproduce this bug. Steps:</p> <p>1. Start mininet (with TreeTopo, size 3)<br/> 2. Stop mininet (in this phase, inventory was always perfectly cleaned)<br/> 3. Start mininet again with same parameters<br/> 4. Stop mininet again (now, some parts of operational inventory are still present, and not fully cleaned)</p> <p>So, bug is still present, and is appearing constantly, so going to look at it.</p> <p>GERRIT: <a href="https://git.opendaylight.org/gerrit/#/c/40299" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/40299</a></p> <p>Right, you can clearly see this issue here:</p> <p><a href="https://jenkins.opendaylight.org/releng/view/CSIT-3node/job/openflowplugin-csit-3node-clustering-only-beryllium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/CSIT-3node/job/openflowplugin-csit-3node-clustering-only-beryllium/</a></p> <p>In 2 first test suites, there is 1 consistent failure when checking for operational after mininet disconnects. This is currently only happening with Li plugin (in the past I saw it also in He).</p> <p>BR/Luis</p> <p>after retest issue is no longer present, closing</p> Duplicate OPNFLWPLUG-568 Development External issue ID 5987 External issue URL Rank 0|i032sn: