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-759 OpenFlowPlugin <p>l2switch csit is not stable in boron:</p> <p><a href="https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/</a></p> <p>however tests pass if we add some time between disconnect and connect mininet between tests:</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/44799/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/44799/</a></p> <p>This explains why testing manually does not show any issue.</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-759

l2switch addresss tracker does not behave normally when mininet is disconnected and connected with no time in-between

Bug Resolved Done Luis Gomez Luis Gomez Mon, 29 Aug 2016 23:32:49 +0000 Mon, 27 Sep 2021 09:01:53 +0000 Mon, 6 Mar 2017 00:34:47 +0000 General 0 7 <p>Openflowplugin project might be right place for the bug.</p> <p>l2switch csit jobs fail because of this bug. Can you please address the issue.</p> <p>Since manually we are not seeing any issues , do we add a delay between the switch disconnect and connect ?</p> <p>No no no, this is a problem. I think it is related to <a href="https://jira.opendaylight.org/browse/MDSAL-197" title="Switch connection bounce results in wrong ownership change in Singleton" class="issue-link" data-issue-key="MDSAL-197"><del>MDSAL-197</del></a> and 6672, and when that bugs will be fixed, this one will probably be fixed too.</p> <p>(In reply to Tomas Slusny from comment #4)<br/> &gt; No no no, this is a problem. I think it is related to <a href="https://jira.opendaylight.org/browse/MDSAL-197" title="Switch connection bounce results in wrong ownership change in Singleton" class="issue-link" data-issue-key="MDSAL-197"><del>MDSAL-197</del></a> and 6672, and<br/> &gt; when that bugs will be fixed, this one will probably be fixed too.</p> <p>ok sure</p> <p>Read my last reply in <a href="https://jira.opendaylight.org/browse/OPNFLWPLUG-767" title="Switch connection bounce generates wrong entity owner in cluster env" class="issue-link" data-issue-key="OPNFLWPLUG-767"><del>OPNFLWPLUG-767</del></a></p> <p>Based on the comments, I believe this bug is targeted for Boron.</p> <p>Based on the comment on the email thread below, this bug is being retargeted for Boron-SR2:</p> <p><a href="https://lists.opendaylight.org/pipermail/l2switch-dev/2016-October/001322.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/l2switch-dev/2016-October/001322.html</a></p> <p>Based on the comment in the mail thread below this bug is targeted for Boron-SR3:<br/> <a href="https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-December/006456.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-December/006456.html</a></p> <p>I will set importance to CRITICAL because as far as I can tell there is no traffic impact but a change in the address-tracker behavior: host addresses are observed in ports besides the port the host is connected to.</p> <p>See mail thread:</p> <p><a href="https://lists.opendaylight.org/pipermail/l2switch-dev/2016-October/001322.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/l2switch-dev/2016-October/001322.html</a></p> <p>Luis &amp; Sai,</p> <p>Is this fixed? Tomas seems to have said that once <a href="https://jira.opendaylight.org/browse/MDSAL-197" title="Switch connection bounce results in wrong ownership change in Singleton" class="issue-link" data-issue-key="MDSAL-197"><del>MDSAL-197</del></a> and <a href="https://jira.opendaylight.org/browse/OPNFLWPLUG-767" title="Switch connection bounce generates wrong entity owner in cluster env" class="issue-link" data-issue-key="OPNFLWPLUG-767"><del>OPNFLWPLUG-767</del></a> are fixed - then this will be fixed. Now both those bugs are fixed - so good to recheck it.</p> <p>Abhijit</p> <p>So l2switch issue seems to be fixed but very recently so I believe it was something else other than the 2 patches you mention:</p> <p><a href="https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/</a></p> Blocks MDSAL-197 Development External issue ID 6575 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i0334v: