<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:05:44 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[L2SWITCH-31] Loop Remover only works 1 time after controller starts</title>
                <link>https://jira.opendaylight.org/browse/L2SWITCH-31</link>
                <project id="10134" key="L2SWITCH">l2switch</project>
                    <description>&lt;p&gt;Loop remover only works first time you bring mininet after controller starts, second and sucesive times does not work.&lt;/p&gt;

&lt;p&gt;To reproduce:&lt;/p&gt;

&lt;p&gt;1) Start controller&lt;/p&gt;

&lt;p&gt;2) Start mininet in ring or regular topology like linear&lt;/p&gt;

&lt;p&gt;3) Check port inventory and see loopremover working:&lt;/p&gt;

&lt;p&gt;&amp;lt;node-connector&amp;gt;&lt;br/&gt;
&amp;lt;id&amp;gt;openflow:1:2&amp;lt;/id&amp;gt;&lt;br/&gt;
&amp;lt;status xmlns=&quot;urn:opendaylight:l2switch:loopremover&quot;&amp;gt;forwarding&amp;lt;/status&amp;gt;&lt;/p&gt;

&lt;p&gt;4) Stop mininet&lt;/p&gt;

&lt;p&gt;5) Start mininet again (same topology used in 2)&lt;/p&gt;

&lt;p&gt;6) Check port inventory, now there is no loopremover in any port &lt;/p&gt;

&lt;p&gt;7) In case of ring topology this will cause packet loop&lt;/p&gt;

&lt;p&gt;BR/Luis&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Linux&lt;br/&gt;
Platform: PC&lt;/p&gt;</environment>
        <key id="21544">L2SWITCH-31</key>
            <summary>Loop Remover only works 1 time after controller starts</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="ecelgp">Luis Gomez</reporter>
                        <labels>
                    </labels>
                <created>Fri, 23 Jan 2015 02:57:32 +0000</created>
                <updated>Thu, 19 Oct 2017 22:33:51 +0000</updated>
                            <resolved>Mon, 22 Jun 2015 18:17:58 +0000</resolved>
                                    <version>unspecified</version>
                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="40307" author="ecelgp" created="Tue, 27 Jan 2015 02:04:07 +0000"  >&lt;p&gt;I will add the comment that in the case of a ring topology, when the loop remover is not present and a host sends a ping, this produces a packet storm not just in the data plane but also on the control plane (l2switch flood flows send traffic to controller). This produces all kind of issues in controller like high CPU, dummy switches after stopping mininet, no host discovery, etc... Only workaround I have seen is to restart controller.&lt;/p&gt;

&lt;p&gt;BR/Luis&lt;/p&gt;</comment>
                            <comment id="40308" author="evanz" created="Tue, 14 Apr 2015 21:13:26 +0000"  >&lt;p&gt;See: &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/18218/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/18218/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In addition to the loss of StpStatus on NodeConnectors it seems this bug has scale impacts as well.&lt;/p&gt;

&lt;p&gt;Before:&lt;br/&gt;
sudo mn --topo tree,7 (127 nodes)&lt;br/&gt;
Failed pings &amp;amp; &quot;DOMRpcRouter-listener-0&quot; java.lang.IllegalArgumentException: Route Identifiers must be supplied&quot; in logs.&lt;/p&gt;

&lt;p&gt;After:&lt;br/&gt;
sudo mn --topo tree,7 (127 nodes)&lt;br/&gt;
16256/16256 success pingall&lt;/p&gt;

&lt;p&gt;sudo mn --topo tree,8 (255 nodes)&lt;br/&gt;
100% success pingall&lt;/p&gt;

&lt;p&gt;at 511 nodes (--topo tree,9) the exception &quot;DOMRpcRouter-listener-0&quot; java.lang.IllegalArgumentException: Route Identifiers must be supplied&quot; reappears and some pings begin to fail.&lt;/p&gt;</comment>
                            <comment id="40309" author="ecelgp" created="Wed, 15 Apr 2015 02:43:29 +0000"  >&lt;p&gt;And you made these perf tests using master code? there are some issues with openflow topology mgr that impacts the l2switch as you can see in the CI test:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/CSIT-1node/job/l2switch-csit-1node-cds-switch-only-master/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/CSIT-1node/job/l2switch-csit-1node-cds-switch-only-master/&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2629</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=2629]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10315"><![CDATA[Lithium]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i01z47:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>