<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:33:39 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>[OPNFLWPLUG-889] Switch disconnect while mastership is being negotiated produces stale switch entry</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-889</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;This only happens in Carbon and it is tracked in the reconciliation suite:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-carbon/614/archives/log.html.gz#s1-s7&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-carbon/614/archives/log.html.gz#s1-s7&lt;/a&gt;&lt;/p&gt;

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

&lt;p&gt;1) Start 3 nodes cluster&lt;/p&gt;

&lt;p&gt;2) Start 1 switch (s1) and connect it to 2 nodes (.101 and .102):&lt;/p&gt;

&lt;p&gt;sudo ovs-vsctl set-controller s1 &quot;tcp:192.168.0.101:6633&quot; &quot;tcp:192.168.0.102:6633&quot;&lt;/p&gt;

&lt;p&gt;3) Block communication owner to switch (in this example .101):&lt;/p&gt;

&lt;p&gt;sudo iptables -A INPUT --source 192.168.0.101 -j DROP&lt;/p&gt;

&lt;p&gt;4) Just after block communication remaining node to switch:&lt;/p&gt;

&lt;p&gt;sudo iptables -A INPUT --source 192.168.0.102 -j DROP&lt;/p&gt;

&lt;p&gt;5) Now observe the following after few seconds:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;The switch closes owner connection (.101).&lt;/li&gt;
	&lt;li&gt;New mastership negotiation starts in remaining node (.102).&lt;/li&gt;
	&lt;li&gt;The switch closes remaining connection (.102).&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The result of the above is an stale switch in operational, only workaround is reboot entire cluster.&lt;/p&gt;

&lt;p&gt;BR/Luis&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="28157">OPNFLWPLUG-889</key>
            <summary>Switch disconnect while mastership is being negotiated produces stale switch entry</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="miroslav.macko">Miroslav Macko</assignee>
                                    <reporter username="ecelgp">Luis Gomez</reporter>
                        <labels>
                    </labels>
                <created>Wed, 10 May 2017 05:00:23 +0000</created>
                <updated>Mon, 27 Sep 2021 09:02:02 +0000</updated>
                            <resolved>Wed, 17 May 2017 21:48:11 +0000</resolved>
                                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="58930" author="ecelgp" created="Tue, 16 May 2017 00:14:52 +0000"  >&lt;p&gt;Also rising this to blocker, this issue is not seen in Boron so we should fix if we can.&lt;/p&gt;</comment>
                            <comment id="58931" author="miroslav.macko" created="Tue, 16 May 2017 08:20:26 +0000"  >&lt;p&gt;Hello Luis,&lt;/p&gt;

&lt;p&gt;I am not able to reproduce it locally on stable/carbon followed your instructions.&lt;/p&gt;

&lt;p&gt;I have checked /restconf/operational/network-topology:network-topology after blocking both controllers, switch closes connections, and operational is clean.&lt;/p&gt;

&lt;p&gt;I have tried to block SLAVE right after MASTER without waiting for new MASTER elected. And also with waiting for new MASTER elected. Topology was cleaned up both times.&lt;/p&gt;

&lt;p&gt;I have checked also Jenkins logs.&lt;br/&gt;
Is it &quot;Check No Switches After Disconnect&quot; what is failing?&lt;br/&gt;
Probably it has no impact, but it looks like there are more switches connected.&lt;br/&gt;
I am only want to be sure, that I am looking to the right place.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Miro&lt;/p&gt;</comment>
                            <comment id="58932" author="ecelgp" created="Tue, 16 May 2017 19:51:37 +0000"  >&lt;p&gt;Hi Miroslav, the issue is still there, see this recent build:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-gate-clustering-only-carbon/49/archives/log.html.gz#s1-s7&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-gate-clustering-only-carbon/49/archives/log.html.gz#s1-s7&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I also realized that sometimes the switch is cleared from operational but it is not from entity owner so when switch reconnects it does not work.&lt;/p&gt;

&lt;p&gt;Please repeat the steps above and when you disconnected slave member just after master member, check entity owner API (I always see slave as master in entity owner when it is not connected).&lt;/p&gt;

&lt;p&gt;Also make sure you block controller to switch communication, not the other way around. If you have problem reproducing I can setup some call and share my desktop.&lt;/p&gt;

&lt;p&gt;BR/Luis&lt;/p&gt;</comment>
                            <comment id="58933" author="miroslav.macko" created="Wed, 17 May 2017 10:26:26 +0000"  >&lt;p&gt;Hello Luis,&lt;/p&gt;

&lt;p&gt;Yes. I am exactly following your instruction. I am blocking controller to switch communication. &lt;/p&gt;

&lt;p&gt;Operational is still clean. But you are right, that entity owner is not.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://10.0.42.201:8181/restconf/operational/entity-owners:entity-owners*&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://10.0.42.201:8181/restconf/operational/entity-owners:entity-owners*&lt;/a&gt;&lt;br/&gt;
&amp;#8212; TYPE &lt;span class=&quot;error&quot;&gt;&amp;#91;org.opendaylight.mdsal.AsyncServiceCloseEntityType&amp;#93;&lt;/span&gt;&lt;br/&gt;
      ID : /a:entity&lt;span class=&quot;error&quot;&gt;&amp;#91;a:name=&amp;#39;openflow:1&amp;#39;&amp;#93;&lt;/span&gt;&lt;br/&gt;
      +-- OWNER: &lt;br/&gt;
&amp;#8212; TYPE &lt;span class=&quot;error&quot;&gt;&amp;#91;org.opendaylight.mdsal.ServiceEntityType&amp;#93;&lt;/span&gt;&lt;br/&gt;
      ID : /a:entity&lt;span class=&quot;error&quot;&gt;&amp;#91;a:name=&amp;#39;openflow:1&amp;#39;&amp;#93;&lt;/span&gt;&lt;br/&gt;
      +-- OWNER:&lt;/p&gt;

&lt;p&gt;Is this what you meant? Or do you check it other way?&lt;/p&gt;

&lt;p&gt;Jozef will try to prepare patch for it.&lt;/p&gt;

&lt;p&gt;Thank you,&lt;br/&gt;
Miro&lt;/p&gt;</comment>
                            <comment id="58934" author="anipbu" created="Wed, 17 May 2017 18:18:12 +0000"  >&lt;p&gt;We are looking to build Carbon RC2 tomorrow 5/18 at 23:59 UTC time assuming there are no blocker bugs.  Is there an ETA for when a fix can be merged and this bug resolved for stable/carbon branch?&lt;/p&gt;</comment>
                            <comment id="58935" author="jozef.bacigal@pantheon.tech" created="Wed, 17 May 2017 18:21:17 +0000"  >&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/57232/9&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/57232/9&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is the patch, Luis can you test it plz ?&lt;/p&gt;

&lt;p&gt;Jozef&lt;/p&gt;</comment>
                            <comment id="58936" author="anipbu" created="Wed, 17 May 2017 21:07:57 +0000"  >&lt;p&gt;(In reply to Jozef Bacigal from comment #6)&lt;br/&gt;
&amp;gt; &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/57232/9&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/57232/9&lt;/a&gt;&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Here is the patch, Luis can you test it plz ?&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Jozef&lt;/p&gt;

&lt;p&gt;This patch is failing to build in jenkins and is still missing +2 from committers.&lt;/p&gt;</comment>
                            <comment id="58937" author="ecelgp" created="Wed, 17 May 2017 21:20:21 +0000"  >&lt;p&gt;Let me test this although patch test does not look very good.&lt;/p&gt;</comment>
                            <comment id="58938" author="ecelgp" created="Wed, 17 May 2017 21:48:11 +0000"  >&lt;p&gt;OK guys, bad and good news.&lt;/p&gt;

&lt;p&gt;BAD:&lt;br/&gt;
The proposed patch: &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/57232&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/57232&lt;/a&gt; has serious issues as shown here: &lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-1node-gate-flow-services-only-nitrogen/60/archives/log.html.gz&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-1node-gate-flow-services-only-nitrogen/60/archives/log.html.gz&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;GOOD:&lt;br/&gt;
It looks like this other patch: &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/57096&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/57096&lt;/a&gt; fixed the issue.&lt;/p&gt;

&lt;p&gt;So I am closing this bug &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.opendaylight.org/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&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>8411</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=8411]]></customfieldvalue>

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

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