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-853 OpenFlowPlugin <p>This is tracked here:</p> <p><a href="https://jenkins.opendaylight.org/releng/view/CSIT-3node/job/openflowplugin-csit-3node-clustering-only-boron/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/CSIT-3node/job/openflowplugin-csit-3node-clustering-only-boron/</a></p> <p>To reproduce:</p> <p>1) Set up 3 cluster node with openflow and table miss features enabled.<br/> 2) Connect OVS switch to 1st node: sudo mn --controller 'remote,ip=192.168.0.101,port=6633' --topo tree,1<br/> 3) check table miss flow in mininet: dpctl dump-flows<br/> 4) stop and start mininet to 2nd node: sudo mn --controller 'remote,ip=192.168.0.102,port=6633' --topo tree,1<br/> 5) check table miss flow in mininet: dpctl dump-flows<br/> 6) Repeat 4) &amp; 5) with 3rd node in the cluster.</p> <p>After the above steps you will realize that only one of the instances (normally the first that is master) is able to push the table miss flow.</p> <p>BR/Luis</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-853

Only 1 cluster instance is able to push table miss flow after initial switch connection

Bug Resolved Done Miroslav Macko Luis Gomez Fri, 10 Feb 2017 00:44:10 +0000 Mon, 27 Sep 2021 09:01:59 +0000 Fri, 14 Apr 2017 16:59:19 +0000 General 0 3 <p>&gt; This is tracked here</p> <p>The recent run only has two failures in suite "030 Cluster Sync Problems".<br/> Which suite does tests the "each mininet connects to different member" scenario?</p> <p><span class="error">&#91;0&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-boron/944/archives/log.html.gz#s1-s6" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-boron/944/archives/log.html.gz#s1-s6</a></p> <p>&gt; recent run only has two failures</p> <p>Carbon has 1 less <span class="error">&#91;1&#93;</span>.</p> <p><span class="error">&#91;1&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-carbon/478/archives/log.html.gz#s1-s6" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-carbon/478/archives/log.html.gz#s1-s6</a></p> <p>There is no spceific TC to catch this bug, it can happen here are there. What matters is that this issue is 1 min to reproduce with steps above and I can add a TC just to check when it gets resolved.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/52115/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/52115/</a></p> <p>Hello Luis,</p> <p>Could you please test this patch?</p> <p>I have tested it locally. It works.</p> <p>Thanks,<br/> Miro</p> <p>We do have automated test for this but the infra is no good since the weekend, I will try in the sandbox and +1 your patch if it works there.</p> <p>By looking at this run, it seems fixed:</p> <p><a href="https://logs.opendaylight.org/sandbox/jenkins091/openflowplugin-csit-3node-clustering-only-carbon/6/archives/log.html.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/sandbox/jenkins091/openflowplugin-csit-3node-clustering-only-carbon/6/archives/log.html.gz</a></p> <p>But looking at the failure, have you rebased you patch lately?</p> <p>Thanks Luis,</p> <p>I have rebased it now.</p> <p>Miro</p> <p>Luis how this fix is running? It can be merged ?</p> <p>It fixes the issue but there is something weird with the switch disconnect test, this patch seems to revert to old cluster behavior of instances disconnected from switch showing as candidate in entity owner:</p> <p><a href="https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-carbon/551/archives/log.html.gz" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-carbon/551/archives/log.html.gz</a></p> <p>Thats why I thought a rebase was needed but i still see the change in the switch disconnect test after rebasing.</p> <p>I think Anil found the reason for the behavior change and -1 the patch.</p> <p>Hi Luis,</p> <p>I have pushed the new patch without the ClusterSingletonService.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/53557" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/53557</a></p> <p>Could you please test it?</p> <p>Thank you,<br/> Miro</p> <p>This is fixed now.</p> Development External issue ID 7770 External issue URL Rank 0|i033pr: