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-442 OpenFlowPlugin <p>This job <a href="https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-cds-config-performance-lithium-redesign-only-master" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-cds-config-performance-lithium-redesign-only-master</a> runs a script which configures 10k flows on 25 switches, then tries to collect stats, removes flows and collect stats again.</p> <p>Having a look into the results from May15 till now, we often have a problem to connect even 25 switches without any flows.</p> <p>During the script run, we loose nodes from inventory<br/> Output before adding flows:<br/> Cycle 0:<br/> Thread 3:<br/> Adding 2000 flows on 25 nodes<br/> Thread 4:<br/> Adding 2000 flows on 25 nodes<br/> Thread 1:<br/> Adding 2000 flows on 25 nodes<br/> Thread 0:<br/> Adding 2000 flows on 25 nodes<br/> Thread 2:<br/> Adding 2000 flows on 25 nodes</p> <p>Output before deleting flows:<br/> Cycle 0:<br/> Thread 2: Deleting 2000 flows on 4 nodes<br/> Thread 3: Deleting 2000 flows on 4 nodes<br/> Thread 0: Deleting 2000 flows on 4 nodes<br/> Thread 1: Deleting 2000 flows on 4 nodes<br/> Thread 4: Deleting 2000 flows on 4 nodes</p> <p>Logs contains lots of WARN and ERROR messages (with stack traces) with different message content.</p> <p>The first NOK behaviour is noticed in the job</p> <p><a href="https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-cds-config-performance-lithium-redesign-only-master/45/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-cds-config-performance-lithium-redesign-only-master/45/</a></p> <p>which uses:<br/> <a href="http://nexus01.dfw.opendaylight.org:8081/nexus/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.3.0-SNAPSHOT/distribution-karaf-0.3.0-20150515.195941-1579.zip" class="external-link" target="_blank" rel="nofollow noopener">http://nexus01.dfw.opendaylight.org:8081/nexus/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.3.0-SNAPSHOT/distribution-karaf-0.3.0-20150515.195941-1579.zip</a></p> <p>The last OK behaviour was in<br/> <a href="https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-cds-config-performance-lithium-redesign-only-master/44/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-cds-config-performance-lithium-redesign-only-master/44/</a></p> <p>with image<br/> <a href="http://nexus01.dfw.opendaylight.org:8081/nexus/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.3.0-SNAPSHOT/distribution-karaf-0.3.0-20150515.192049-1576.zip" class="external-link" target="_blank" rel="nofollow noopener">http://nexus01.dfw.opendaylight.org:8081/nexus/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.3.0-SNAPSHOT/distribution-karaf-0.3.0-20150515.192049-1576.zip</a></p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-442

redesign ofp inventory looses switches after few thousands of flows configured; often a problem to connect 25 switches

Bug Resolved Won't Do Moiz Raja Peter Gubka Mon, 18 May 2015 11:30:24 +0000 Mon, 27 Sep 2021 09:01:31 +0000 Wed, 27 May 2015 12:39:37 +0000 General 0 2 <p>Attachment karaf.log.zip has been added with description: karaf.log.zip</p> <p>On Friday 15 may 2015 I was able to successfully send 3000 flows to OF switch and via flow statistic reply store it to operational datastore.</p> <p>Today I checkout back to my built (when it was possible) 39ca97e292ee5348cac005fe35b7973dfe8a1627 (Ensuring exclusive access to flow registry.). I built it again and currently I am getting lot of warning messages in log:</p> <p> 2015-05-18 14:03:55,393 | WARN | entLoopGroup-8-3 | TransactionProxy | 179 - org.opendaylight.controller.sal-distributed-datastore - 1.2.0.SNAPSHOT | Failed to acquire operation permit for transaction member-1-txn-81733</p> <p>I suppose that problem could be in controller. I will try to build caraf with artifacts from friday.</p> <p>The same log entry is observed also with<br/> odl-openflowplugin-flow-services-rest<br/> feature installed.</p> <p>Could we please add steps to reproduce in here. I am assuming we want 25 switches connected and then the flow blaster script to be run.</p> <p>The links to the jobs are not working.</p> <p>(In reply to Moiz Raja from comment #3)<br/> &gt; Could we please add steps to reproduce in here. I am assuming we want 25<br/> &gt; switches connected and then the flow blaster script to be run.<br/> &gt; <br/> &gt; The links to the jobs are not working.</p> <p>Links are not working, because jenkins' history "moved" forward. In general you can take any later job results</p> <p><a href="https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-cds-config-performance-lithium-redesign-only-master/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-cds-config-performance-lithium-redesign-only-master/</a></p> <p>(In reply to Moiz Raja from comment #3)<br/> &gt; Could we please add steps to reproduce in here. I am assuming we want 25<br/> &gt; switches connected and then the flow blaster script to be run.<br/> &gt; <br/> &gt; The links to the jobs are not working.</p> <p>Regarding steps to reproduce. You can take any build with "yellow" ball and check it's robot results. The test "Are Switches Connected" is failed, because 25 switches managed by mininet are not present in the operational inventory.</p> <p>So steps are, connect 25 switches with mininet and check operational inventory nodes.</p> <p>steps to reproduce:</p> <ul class="alternate" type="square"> <li>start openflowplugin karaf distribution</li> <li>feature:install odl-openflowplugin-flow-services-rest-li</li> <li>start mininet (with e.g. one switch)</li> <li>PUT batch of flows (in my example 1000 flows see enclosure)</li> </ul> <p>Then in karaf log starts to occure following warning repeatedly<br/> 2015-05-19 08:46:03,754 | WARN | entLoopGroup-8-8 | TransactionProxy | 182 - org.opendaylight.controller.sal-distributed-datastore - 1.2.0.SNAPSHOT | Failed to acquire operation permit for transaction member-1-txn-187409</p> <p>Other symptom is problematic connection between controller and switch. Controller gradually stops to response. At the begining controller response on OFPT_HELLO but in the end no response from controller is received.</p> <p>When inserting flows one by one (tested on three flows) then this problem doesn't occure.</p> <p>Attachment flow-1000.xml has been added with description: 1000 flows</p> <p>after merging this patch <br/> <a href="https://git.opendaylight.org/gerrit/#/c/20680/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/20680/</a></p> <p>new problem has occured.</p> <p>When config datastore contains batch of flow (in my <a href="https://jira.opendaylight.org/browse/L2SWITCH-40" title="Ipv4Decoder unable to listen to Ethernet packets" class="issue-link" data-issue-key="L2SWITCH-40">L2SWITCH-40</a>) they are successfully sent to device after it turn on. Also statistics bring this information to controller but it isn't written to database.</p> <p>Karaf log contains flooding of warn logs<br/> 2015-05-19 13:05:12,395 | WARN | entLoopGroup-8-5 | TransactionChainManager | 198 - org.opendaylight.openflowplugin.impl - 0.1.0.SNAPSHOT | failed to put into writeOnlyTransaction : Previous transaction member-1-txn-407757 is not ready yet</p> <p>the initial problem is the problem of ovs versioning discussed in<br/> <a href="https://lists.opendaylight.org/pipermail/integration-dev/2015-May/003282.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/integration-dev/2015-May/003282.html</a></p> <p>the last problem mentioned by Jozef does not happen at this time</p> <p>therefor "closing" the bug</p> Blocks OPNFLWPLUG-429 OPNFLWPLUG-443 OVSDB-156 Development External issue ID 3249 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i0316f: