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-865 OpenFlowPlugin <p>Zero flows populated in switches when connected to Leader Node.</p> <p>Flows : 10k flows/switch<br/> Switches : 15</p> <p>Steps to Reproduce :<br/> ====================<br/> 1. Get Inventory Follower and Leader information</p> <p>2. Start Mininet Connect To Follower Node1</p> <p>3. Add Bulk Flow from follower node1</p> <p>4. Get Bulk Flows and Verify In Cluster config DS and verify all flows are installed</p> <p>5. Verify Default flows in switches when connected to Follower node. Here it shows zero flows in all 15 switches </p> <p>6. Verify Flows In Switch when connected to Follower Node . </p> <p>7. Flows will get installed when connected to Follower node.</p> <p>8. Stop and start mininet to Leader Node.</p> <p>9. Verify Flows in switch when connected to Leader Node . </p> <p>10. Issue is consistent . Zero flows will be installed in all 15 switches when connected to Leader Node.</p> <p>When connected to Follower node1 , populated total flows in all switches (150000.0)<br/> After stop and start mininet when connected to Follower Node , populated total flows in all switches (150000.0)<br/> Stop and start mininet connect to Leader node</p> <p>sudo mn --controller 'remote,ip=10.29.12. <br/> 213,port=6633' --topo linear,15 --switch ovsk,protocols=OpenFlow13</p> <p>Zero flows populated when connected to Leader Node.(0.0 != 150000.0)</p> <p>given log file : <a href="https://jenkins.opendaylight.org/sandbox/job/openflowplugin-csit-3node-periodic-bulkomatic-clustering-daily-only-boron/6/robot/report/log.html" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/sandbox/job/openflowplugin-csit-3node-periodic-bulkomatic-clustering-daily-only-boron/6/robot/report/log.html</a></p> <p>Operating System: Linux<br/> Platform: All</p> OPNFLWPLUG-865

Zero flows populated in all switches when connected to Leader Node.

Bug Resolved Done Luis Gomez Naveen kumar Thatipalli Tue, 7 Mar 2017 12:19:13 +0000 Mon, 27 Sep 2021 09:02:00 +0000 Thu, 13 Apr 2017 16:31:43 +0000 General 0 5 <p>Attachment zero_flows_installed_when_connected_to_Leader_Node_boron_latest.mht has been added with description: Log file for zero flows in 15 switches connected to Leader Node</p> <p>Is this not duplicate of <a href="https://bugs.opendaylight.org/show_bug.cgi?id=7884?" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=7884?</a></p> <p>Hi Luis,<br/> This is not duplicate of bug &lt;7884&gt;.<br/> 7884 : Some of the switches are not getting installed with flows . Zero flows will be present in few switches. This happens when connected to Follower and Leader Node as well.<br/> Example: 4 out of 15 switches will have zero flows.</p> <p>7915 : All switches will be having zero flows when connected to Leader Node only. This issue is consistently reproducing.</p> <p>Regards,<br/> Naveen.</p> <p>OK, one question: can you reproduce this issue in some local environment or only in ODL jenkins?</p> <p>Also, now I realize you are using vey high # flows (150K), does the issue reproduces with less number (e.g. 15K)?</p> <p>Hi Luis,<br/> Executed with less number of flows and given below log file. Issue is getting reproduced when connected to Leader Node.</p> <p>Flows per switch : 10000<br/> switches: 1<br/> Total flows : 10000</p> <p>log snippet:<br/> ============<br/> Keyword 'MininetKeywords.Check Flows In Mininet' failed after retrying for 4 minutes 10 seconds. The last error was: 0.0 != 10000.0</p> <p>Build : <a href="https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.5.3-SNAPSHOT/distribution-karaf-0.5.3-20170312.234446-802.zip" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.5.3-SNAPSHOT/distribution-karaf-0.5.3-20170312.234446-802.zip</a></p> <p>Attached Log file for the same.</p> <p>Regards,<br/> Naveen.</p> <p>Executed in latest build with single switch with 10k flows. Able to reproduce issue and attached log file.</p> <p>Attachment 010_small_config_single_switch_10k_flows_SF142_march_13th_2017.mht has been added with description: Latest log with 10000 flows with single switch</p> <p>Right, this also reproduces easily with 1 switch and 10K flows, I believe this bug is connected with <a href="https://bugs.opendaylight.org/show_bug.cgi?id=7884" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=7884</a> as both share same scenario of switch reconnecting from no-leader to leader.</p> <p>I think this could be a duplicate of <a href="https://bugs.opendaylight.org/show_bug.cgi?id=7884" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=7884</a>, therefore blocker too.</p> <p>Reproduce is as simple as:</p> <p>1) Start 1 controller<br/> 2) Start mininet: sudo mn --controller 'remote,ip=192.168.0.1,port=6633' --topo linear,1<br/> 3) Push 10K flows: python ./odl_tester.py --threads 5 --flows 10000 --fpr 100 --no-delete<br/> 4) Stop and start mininet<br/> 5) check flows in switch: mininet&gt; dpctl dump-aggregate -O OpenFlow13</p> <p>2 additional notes:</p> <ul class="alternate" type="square"> <li>The issue does not show when I enable FRS.</li> <li>The regression was introduced after Boron SR2 and is present on both Boron and master branches.</li> </ul> <p>Hi Luis/Naveen,</p> <p>I pushed the following patch that fixes this issue</p> <p><a href="https://git.opendaylight.org/gerrit/53383" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/53383</a></p> <p>Can you please take this patch try to recreate the issue again? I locally tried using the instruction that luis provided and it works for me.</p> <p>carbon :<a href="https://git.opendaylight.org/gerrit/#/c/53521/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/53521/</a></p> <p>Reopen issue for carbon. Carbon fails the following tests for single controller (4 cpus):</p> <p>10K flows in 1 switch:</p> <p>1) Start 1 controller<br/> 2) Start mininet: sudo mn --controller 'remote,ip=192.168.0.1,port=6633' --topo linear,1<br/> 3) Push 10K flows: python ./odl_tester.py --threads 5 --flows 10000 --fpr 100 --no-delete<br/> 4) Stop and start mininet<br/> 5) check flows in switch: mininet&gt; dpctl dump-aggregate -O OpenFlow13</p> <p>20K flows in 8 switch:</p> <p>1) Start 1 controller<br/> 2) Start mininet: sudo mn --controller 'remote,ip=192.168.0.1,port=6633' --topo linear,8<br/> 3) Push 20K flows: python ./odl_tester.py --threads 5 --flows 20000 --fpr 100 --no-delete<br/> 4) Stop and start mininet<br/> 5) check flows in switch: mininet&gt; dpctl dump-aggregate -O OpenFlow13</p> <p>I tested this on this patch: <a href="https://git.opendaylight.org/gerrit/#/c/53972/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/53972/</a> and it is working. On master it is not, so this issue was probably caused by DeviceFlowRegistry performance regression.</p> <p>Can you recheck this please Luis after my patches that fixed regression in 6917 was merged?</p> <p>Yes, this is fixed now.</p> Development External issue ID 7915 External issue URL Rank 0|i033sf: