<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55: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>[CONTROLLER-1478] Switch reconciliation is not happening after leader node restart in 3 node cluster</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1478</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;Build used        : &lt;br/&gt;
===================&lt;br/&gt;
Karaf distro from ODL Beryllium master code&lt;/p&gt;

&lt;p&gt;Test Type         : &lt;br/&gt;
===================&lt;br/&gt;
Switch reconciliation is not happening after leader node restart in 3 node cluster.&lt;/p&gt;

&lt;p&gt;Objective of test : &lt;br/&gt;
===================&lt;br/&gt;
verify Switch reconciliation when leader node is restarted. &lt;/p&gt;

&lt;p&gt;Test Steps :&lt;br/&gt;
============&lt;br/&gt;
1. Bring up healthy 3 node cluster. &lt;br/&gt;
2. c1, c2 and c3 nodes are up. c1 is leader for config and operational inventory shard.&lt;br/&gt;
3. push 1000 flows from leader node c1 to 3 switchs (s1,s2 and s3).&lt;br/&gt;
4. connect 1 switch per node to c1, c2 and c3 node. (switch s1 connected to c1, switch s2 connected to c2 and switch s3 connected to c3)&lt;br/&gt;
5. total flows in 3 switchs is 3000&lt;br/&gt;
6. disconnect switch s1 from c1 node.&lt;br/&gt;
7. stop c1 node&lt;br/&gt;
8. push 200 more flows from leader node c1 to 3 switchs.&lt;br/&gt;
9. start c1 node&lt;br/&gt;
10. now c3 node is leader for config inventory shard and c2 is leader for operational inventory shard.&lt;br/&gt;
11. checked total flows in config data store is 3000 but expected is 3600&lt;br/&gt;
12. reconnect switchs s1 to c1 node.&lt;br/&gt;
13. total flows in reconnected switch s1 is 0 but expected number of flows is 1200 after resync.&lt;/p&gt;

&lt;p&gt;Note: &lt;br/&gt;
 1. there is AskTimeOutException in c3 node after step 7 (refer logs in folder jan29_till_step7).&lt;br/&gt;
 2. after step 12, there is AskTimeOutException exception in node c1 (refer logs in folder jan29_till_step12).&lt;/p&gt;

&lt;p&gt;Controllers (to cross-check logs):&lt;br/&gt;
===================================&lt;br/&gt;
c1 - Controller 1 with IP 10.183.181.41 &lt;br/&gt;
c2 - Controller 2 with IP 10.183.181.42 &lt;br/&gt;
c3 - Controller 3 with IP 10.183.181.43  &lt;/p&gt;

&lt;p&gt;Enclosed Logs:&lt;br/&gt;
==============&lt;br/&gt;
c1.log for controller c1&lt;br/&gt;
c2.log for controller c2&lt;br/&gt;
c3.log for controller c3&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26032">CONTROLLER-1478</key>
            <summary>Switch reconciliation is not happening after leader node restart in 3 node cluster</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="imanilyadav@gmail.com">Anil Gujele</reporter>
                        <labels>
                    </labels>
                <created>Fri, 29 Jan 2016 04:30:58 +0000</created>
                <updated>Thu, 19 Oct 2017 22:33:47 +0000</updated>
                            <resolved>Thu, 25 Feb 2016 01:25:01 +0000</resolved>
                                    <version>Beryllium</version>
                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                                                                <comments>
                            <comment id="51237" author="imanilyadav@gmail.com" created="Fri, 29 Jan 2016 04:30:58 +0000"  >&lt;p&gt;Attachment resyncFailed3SwitchLeaderRestart.rar has been added with description: attached logs from c1, c2,c3 node.&lt;/p&gt;</comment>
                            <comment id="51227" author="imanilyadav@gmail.com" created="Fri, 29 Jan 2016 05:54:47 +0000"  >&lt;p&gt;In step-8, flow is pushed from node c3. &lt;br/&gt;
Corrected step-8: &lt;br/&gt;
8. push 200 more flows from leader node c3 to 3 switchs.&lt;/p&gt;</comment>
                            <comment id="51228" author="ecelgp" created="Sun, 31 Jan 2016 03:03:21 +0000"  >&lt;p&gt;I can easily reproduce issue in 13 by:&lt;/p&gt;

&lt;p&gt;1) Push a normal switch flow (do not connect a switch for now)&lt;/p&gt;

&lt;p&gt;2) Kill and recover the inventory shard leader&lt;/p&gt;

&lt;p&gt;3) Connect switch to old shard leader - Flow is not programmed&lt;/p&gt;</comment>
                            <comment id="51229" author="ecelgp" created="Sun, 31 Jan 2016 03:07:10 +0000"  >&lt;p&gt;Anil, is this the cluster RPC issue you commented to me?&lt;/p&gt;</comment>
                            <comment id="51230" author="vishnoianil@gmail.com" created="Sun, 31 Jan 2016 04:06:51 +0000"  >&lt;p&gt;Yes luis.&lt;/p&gt;</comment>
                            <comment id="51231" author="imanilyadav@gmail.com" created="Tue, 2 Feb 2016 12:21:54 +0000"  >&lt;p&gt;I have verified this defect with build from latest ODL Berrilium master code, reconciliation is working in this scenario.&lt;/p&gt;

&lt;p&gt;I see below log messages in other two nodes in every 5 seconds once leader node is down.&lt;/p&gt;

&lt;p&gt;2016-02-02 03:51:05,862 | WARN  | ds-oper-thread-0 | OperationLimiter                 | 143 - org.opendaylight.controller.sal-distributed-datastore - 1.3.0.SNAPSHOT | Failed to acquire operation permit for transaction member-3-chn-11-txn-2021&lt;br/&gt;
2016-02-02 03:51:10,863 | WARN  | ds-oper-thread-0 | OperationLimiter                 | 143 - org.opendaylight.controller.sal-distributed-datastore - 1.3.0.SNAPSHOT | Failed to acquire operation permit for transaction member-3-chn-11-txn-2021&lt;br/&gt;
2016-02-02 03:51:15,863 | WARN  | ds-oper-thread-0 | OperationLimiter                 | 143 - org.opendaylight.controller.sal-distributed-datastore - 1.3.0.SNAPSHOT | Failed to acquire operation permit for transaction member-3-chn-11-txn-2021&lt;/p&gt;</comment>
                            <comment id="51232" author="rgoulding" created="Tue, 9 Feb 2016 13:29:20 +0000"  >&lt;p&gt;So this works?&lt;/p&gt;</comment>
                            <comment id="51233" author="vishnoianil@gmail.com" created="Tue, 9 Feb 2016 18:00:39 +0000"  >&lt;p&gt;Hi Anil,&lt;/p&gt;

&lt;p&gt;Can you please test with the latest stable/beryllium, it should be fixed with &lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/34115/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/34115/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;</comment>
                            <comment id="51234" author="imanilyadav@gmail.com" created="Thu, 11 Feb 2016 13:17:34 +0000"  >&lt;p&gt;Hi Anil,&lt;/p&gt;

&lt;p&gt; I have tested it with your patch and it again happened in second attempt.&lt;/p&gt;

&lt;p&gt;Thanks&lt;br/&gt;
 ANil&lt;/p&gt;</comment>
                            <comment id="51235" author="rgoulding" created="Tue, 16 Feb 2016 16:15:48 +0000"  >&lt;p&gt;Is this actually fixed?  Is this still a blocker?  If this is still causing issues, cna you please reopen.&lt;/p&gt;</comment>
                            <comment id="51236" author="tpantelis" created="Thu, 25 Feb 2016 01:25:01 +0000"  >&lt;p&gt;I haven&apos;t heard anything wrt this still being an issue after Anil&apos;s patch. Closing...&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13564" name="resyncFailed3SwitchLeaderRestart.rar" size="248533" author="imanilyadav@gmail.com" created="Fri, 29 Jan 2016 04:30:58 +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>5135</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=5135]]></customfieldvalue>

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

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