<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:33:14 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-728] Entity Owner not resolved properly after owner is isolated or rejoined with iptables</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-728</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;To reproduce install controller cluster in Be or B and:&lt;/p&gt;

&lt;p&gt;1) Connect switch to 3 nodes&lt;br/&gt;
2) Find out switch owner&lt;br/&gt;
3) isolate owner from other nodes using iptables:&lt;br/&gt;
sudo iptables -A OUTPUT -d &lt;/p&gt;
{other-controller-IP} -j DROP&lt;br/&gt;
sudo iptables -A OUTPUT -d {other-controller-IP}
&lt;p&gt; -j DROP&lt;br/&gt;
4) Check entity ownership in cluster node&lt;br/&gt;
5) after a while rejoin the cluster:&lt;br/&gt;
sudo iptables -D OUTPUT -d &lt;/p&gt;
{other-controller-IP} -j DROP&lt;br/&gt;
sudo iptables -D OUTPUT -d {other-controller-IP}
&lt;p&gt; -j DROP&lt;br/&gt;
6) Check entity ownership in cluster node&lt;/p&gt;

&lt;p&gt;Either 4) or 6) fails sporadically.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="27996">OPNFLWPLUG-728</key>
            <summary>Entity Owner not resolved properly after owner is isolated or rejoined with iptables</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, 8 Jul 2016 21:43:05 +0000</created>
                <updated>Mon, 27 Sep 2021 09:01:51 +0000</updated>
                            <resolved>Wed, 26 Oct 2016 12:17:45 +0000</resolved>
                                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>10</watches>
                                                                                                                <comments>
                            <comment id="58053" author="vishnoianil@gmail.com" created="Fri, 8 Jul 2016 22:03:55 +0000"  >&lt;p&gt;Hi Luis,&lt;/p&gt;

&lt;p&gt;Is this for He plugin or Li plugin or both?&lt;/p&gt;</comment>
                            <comment id="58054" author="ecelgp" created="Fri, 8 Jul 2016 22:26:20 +0000"  >&lt;p&gt;Both, see the mail I just sent.&lt;/p&gt;</comment>
                            <comment id="58055" author="shuva.jyoti.kar.87@gmail.com" created="Thu, 21 Jul 2016 17:08:48 +0000"  >&lt;p&gt;Luis , is this issue observed with OF-HA ?&lt;/p&gt;</comment>
                            <comment id="58056" author="shuva.jyoti.kar.87@gmail.com" created="Thu, 21 Jul 2016 17:16:33 +0000"  >&lt;p&gt;Also Luis, is this issue sporadic or consistent ?&lt;/p&gt;</comment>
                            <comment id="58057" author="ecelgp" created="Thu, 21 Jul 2016 17:39:01 +0000"  >&lt;p&gt;If you see above, switch connects to the 3 nodes.&lt;/p&gt;

&lt;p&gt;It is consistently happening with Li plugin and lately very rare in He plugin.&lt;/p&gt;</comment>
                            <comment id="58058" author="arthi.b@hcl.com" created="Fri, 29 Jul 2016 09:23:44 +0000"  >&lt;p&gt;Hi Luis,&lt;/p&gt;

&lt;p&gt;Following are the procedure I have followed for the bug:&lt;br/&gt;
&#8226; Got the latest beryllium distribution.&lt;br/&gt;
&#8226; Installed openflowplugin features.&lt;br/&gt;
&#8226; Added bridge and set controllers to the nodes. [&lt;span class=&quot;error&quot;&gt;&amp;#91;Control node and two compute nodes&amp;#93;&lt;/span&gt;]&lt;br/&gt;
  &lt;span class=&quot;error&quot;&gt;&amp;#91;stack@compute2 devstack&amp;#93;&lt;/span&gt;$ sudo ovs-vsctl --no-wait add-br br-int&lt;br/&gt;
  &lt;span class=&quot;error&quot;&gt;&amp;#91;stack@compute2 devstack&amp;#93;&lt;/span&gt;$ sudo ovs-vsctl set bridge br-int protocols=&lt;span class=&quot;error&quot;&gt;&amp;#91;&amp;quot;OpenFlow13&amp;quot;&amp;#93;&lt;/span&gt;&lt;br/&gt;
  &lt;span class=&quot;error&quot;&gt;&amp;#91;stack@compute2 devstack&amp;#93;&lt;/span&gt;$ sudo ovs-vsctl set-controller br-int tcp:10.106.138.154:6653  tcp:10.106.138.155:6653  tcp:10.106.138.110:6653&lt;br/&gt;
&#8226; Isolate owner from other nodes using iptables.&lt;br/&gt;
  sudo iptables -A OUTPUT -d 10.106.138.110 -j DROP&lt;br/&gt;
  sudo iptables -A OUTPUT -d 10.106.138.154 -j DROP&lt;br/&gt;
The members are removed from the entity.&lt;br/&gt;
&#8226; Rejoin the controllers to the cluster.&lt;br/&gt;
  sudo iptables -D OUTPUT -d 10.106.138.110 -j DROP&lt;br/&gt;
  sudo iptables -D OUTPUT -d 10.106.138.154 -j DROP&lt;br/&gt;
The members are getting added to the entity as candidates. &lt;br/&gt;
PFA for the entity owner observation.&lt;/p&gt;

&lt;p&gt;Since you has mentioned, this bug is sporadically reproduced, I repeated the tests for 3 times each. (Li and He Plugin).&lt;br/&gt;
The members are isolated and rejoined properly from/to the entity list.&lt;/p&gt;

&lt;p&gt;Queries:&lt;br/&gt;
1. You have mentioned &#8220;Either 4) or 6) fails&#8221;. Is that fails means, the members are not isolated or rejoined properly from/to the entity list?&lt;br/&gt;
2. Should I look at CSIT regarding this bug? &lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Arthi&lt;/p&gt;</comment>
                            <comment id="58068" author="arthi.b@hcl.com" created="Fri, 29 Jul 2016 09:23:44 +0000"  >&lt;p&gt;Attachment Bug#6177_Observation.txt has been added with description: Entity Owner Observation Document&lt;/p&gt;</comment>
                            <comment id="58059" author="ecelgp" created="Tue, 2 Aug 2016 04:36:42 +0000"  >&lt;p&gt;OK, lets track the yellow builds on this job (the red are infra issues):&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-3node-clustering-only-beryllium/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-3node-clustering-only-beryllium/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As I commented before, the issue seems to happen very much with the Boron (Li redesign) plugin but not often with Beryllium (He redesign).&lt;/p&gt;</comment>
                            <comment id="58060" author="andrejleitner" created="Tue, 9 Aug 2016 12:01:11 +0000"  >&lt;p&gt;Hi guys, this should be solved within &lt;a href=&quot;https://jira.opendaylight.org/browse/OPNFLWPLUG-659&quot; title=&quot;Milestone: integrate with Singleton app. Controller multiphase&quot; class=&quot;issue-link&quot; data-issue-key=&quot;OPNFLWPLUG-659&quot;&gt;&lt;del&gt;OPNFLWPLUG-659&lt;/del&gt;&lt;/a&gt;.&lt;br/&gt;
(using cluster singleton service instead of EOS)&lt;/p&gt;</comment>
                            <comment id="58061" author="miroslav.macko" created="Thu, 25 Aug 2016 15:59:31 +0000"  >&lt;p&gt;We have tested &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/44664/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/44664/&lt;/a&gt; and there are still issues. Jozef will continue working on that. It is not needed to merge it yet.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Miro&lt;/p&gt;</comment>
                            <comment id="58062" author="ecelgp" created="Thu, 25 Aug 2016 16:04:05 +0000"  >&lt;p&gt;The issue of isolate + rejoin is present in Beryllium -&amp;gt; It is not regression in Boron -&amp;gt; It is not blocker. Still good to fix if we can.&lt;/p&gt;</comment>
                            <comment id="58063" author="andrejleitner" created="Wed, 31 Aug 2016 13:21:50 +0000"  >&lt;p&gt;Marked as dependent on &lt;a href=&quot;https://jira.opendaylight.org/browse/MDSAL-195&quot; title=&quot;ClusterSingletonService is not closed after Leader moves to IsolatedLeader&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MDSAL-195&quot;&gt;&lt;del&gt;MDSAL-195&lt;/del&gt;&lt;/a&gt; which is probably the real cause.&lt;/p&gt;</comment>
                            <comment id="58064" author="ecelgp" created="Tue, 13 Sep 2016 02:47:56 +0000"  >&lt;p&gt;After fixing the test, the latest and probably the only issue observed is a change in the owner when an instance is rejoined to the cluster, like for example if a rejoin member 1 that was previously isolated, the device owner changes from 2 to 3. Kind of weird but this is what I see in the test.&lt;/p&gt;</comment>
                            <comment id="58065" author="arthi.b@hcl.com" created="Sat, 17 Sep 2016 12:03:18 +0000"  >&lt;p&gt;Setup:&lt;br/&gt;
1 control and 2 compute nodes&lt;/p&gt;

&lt;p&gt;Distro: distribution-karaf-0.4.4-20160916.220725-251.tar.gz&lt;/p&gt;

&lt;p&gt;I&apos;ve tested the scenario and observed the ownership is not been changed. &lt;br/&gt;
Say, &lt;br/&gt;
&quot;candidate&quot;:[&lt;/p&gt;
{&quot;name&quot;:&quot;member-1&quot;}
&lt;p&gt;,&lt;/p&gt;
{&quot;name&quot;:&quot;member-2&quot;}
&lt;p&gt;,&lt;/p&gt;
{&quot;name&quot;:&quot;member-3&quot;}
&lt;p&gt;],&quot;owner&quot;:&quot;member-1&quot;}&lt;/p&gt;

&lt;p&gt;I&apos;m isolating the member-1&lt;br/&gt;
sudo iptables -A OUTPUT -d 10.106.138.136 -j DROP&lt;/p&gt;

&lt;p&gt;Then member-2 becomes owner. &lt;/p&gt;

&lt;p&gt;And while rejoining member-1&lt;br/&gt;
sudo iptables -D OUTPUT -d 10.106.138.136 -j DROP&lt;/p&gt;

&lt;p&gt;The ownership is not been changed, It&apos;s still member-2&lt;br/&gt;
I&apos;ve tested for 3 times. I observed the same result.&lt;/p&gt;</comment>
                            <comment id="58069" author="arthi.b@hcl.com" created="Sat, 17 Sep 2016 12:04:01 +0000"  >&lt;p&gt;Attachment 6177.txt has been added with description: 6177_observation&lt;/p&gt;</comment>
                            <comment id="58066" author="ecelgp" created="Fri, 7 Oct 2016 19:45:54 +0000"  >&lt;p&gt;So it is been a while I do not look at this issue and I think you are right, I do not see the change of owner anymore but I still see some sporadic failures of isolated member not joining the cluster when iptables rule is deleted:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-boron/724/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-3node-clustering-only-boron/724/archives/log.html.gz&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="58067" author="vdemcak@cisco.com" created="Thu, 13 Oct 2016 08:34:18 +0000"  >&lt;p&gt;Manual testing and carbon/boron jenkin&apos;s jobs look ok.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="27017">MDSAL-195</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="28023">OPNFLWPLUG-755</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="14072" name="6177.txt" size="3583" author="arthi.b@hcl.com" created="Sat, 17 Sep 2016 12:04:01 +0000"/>
                            <attachment id="14071" name="Bug#6177_Observation.txt" size="4784" author="arthi.b@hcl.com" created="Fri, 29 Jul 2016 09:23:44 +0000"/>
                    </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>6177</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=6177]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

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

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