<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:14:28 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>[NETCONF-220] Getting content from cluster from the second follower causes an &quot;AskTimeoutException&quot;</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-220</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;Attempting to fetch data from the second follower in a 3-node cluster when original owner is down, causes a java exception to be returned in the response text:&lt;/p&gt;

&lt;p&gt;&amp;lt;errors xmlns=&quot;urn:ietf:params:xml:ns:yang:ietf-restconf&quot;&amp;gt;&amp;lt;error&amp;gt;&amp;lt;error-type&amp;gt;application&amp;lt;/error-type&amp;gt;&amp;lt;error-tag&amp;gt;operation-failed&amp;lt;/error-tag&amp;gt;&amp;lt;error-message&amp;gt;Problem to get data from transaction.&amp;lt;/error-message&amp;gt;&amp;lt;error-info&amp;gt;akka.pattern.AskTimeoutException: Ask timed out on [Actor&lt;span class=&quot;error&quot;&gt;&amp;#91;akka.tcp://opendaylight-cluster-data@10.29.11.243:2550/user/topology-netconf/netconf-test-device/mountpoint#1234942408&amp;#93;&lt;/span&gt;] after &lt;span class=&quot;error&quot;&gt;&amp;#91;5000 ms&amp;#93;&lt;/span&gt;&lt;br/&gt;
	at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:334)&lt;br/&gt;
	at akka.actor.Scheduler$$anon$7.run(Scheduler.scala:117)&lt;br/&gt;
	at scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:599)&lt;br/&gt;
	at scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)&lt;br/&gt;
	at scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:597)&lt;br/&gt;
	at akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(Scheduler.scala:467)&lt;br/&gt;
	at akka.actor.LightArrayRevolverScheduler$$anon$8.executeBucket$1(Scheduler.scala:419)&lt;br/&gt;
	at akka.actor.LightArrayRevolverScheduler$$anon$8.nextTick(Scheduler.scala:423)&lt;br/&gt;
	at akka.actor.LightArrayRevolverScheduler$$anon$8.run(Scheduler.scala:375)&lt;br/&gt;
	at java.lang.Thread.run(Thread.java:745)&lt;br/&gt;
&amp;lt;/error-info&amp;gt;&amp;lt;/error&amp;gt;&amp;lt;/errors&amp;gt;&lt;/p&gt;

&lt;p&gt;The response code returned is 500.&lt;br/&gt;
The URI requested was: /restconf/config/network-topology:network-topology/topology/topology-netconf/node/netconf-test-device/yang-ext:mount&lt;/p&gt;

&lt;p&gt;The request is successful when the first follower (the new owner) is querried&lt;/p&gt;

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

&lt;p&gt;Test to look for is in &quot;Entity&quot; suite under the name &quot;Check_Config_Data_Before_Modification_With_Original_Owner_Down&quot;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21233">NETCONF-220</key>
            <summary>Getting content from cluster from the second follower causes an &quot;AskTimeoutException&quot;</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="10003">Cannot Reproduce</resolution>
                                        <assignee username="rudolf.brisuda@pantheon.tech">Rudolf Brisuda</assignee>
                                    <reporter username="erdeak@cisco.com">Ernest De&#225;k</reporter>
                        <labels>
                    </labels>
                <created>Wed, 15 Jun 2016 12:12:12 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:26 +0000</updated>
                            <resolved>Mon, 24 Oct 2016 13:12:53 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="39468" author="jmorvay@cisco.com" created="Thu, 16 Jun 2016 07:37:53 +0000"  >&lt;p&gt;Hi Ernest,&lt;/p&gt;

&lt;p&gt;This can be another symptom of &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-187&quot; title=&quot;Clustering: Akka timeout after node outage&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-187&quot;&gt;&lt;del&gt;NETCONF-187&lt;/del&gt;&lt;/a&gt; although with much simpler bug replication steps.&lt;/p&gt;</comment>
                            <comment id="39469" author="rudolf.brisuda@pantheon.tech" created="Mon, 5 Sep 2016 15:34:16 +0000"  >&lt;p&gt;I am unable to reproduce.&lt;br/&gt;
I did these steps:&lt;br/&gt;
1. inserting data on the one node,&lt;br/&gt;
2. shutting down master node,&lt;br/&gt;
3. checking data on the remaining nodes.&lt;/p&gt;

&lt;p&gt;At both nodes I got 200 OK with inserted data.&lt;/p&gt;</comment>
                            <comment id="39470" author="vrpolak" created="Mon, 10 Oct 2016 14:25:14 +0000"  >&lt;p&gt;This is still happening frequently in CSIT. Recent Boron example: Created data is seen on a follower (member-1) &lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt;, but after entity owner (member-2) is killed, data is seen as empty &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt;.&lt;/p&gt;

&lt;p&gt;Compared to the original description, there is no AskTimeoutException visible in the follower karaf.log but there are several warnings visible on the new owner (member-3) karaf.log &lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt; during the critical 26th minute.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-boron/263/archives/log.html.gz#s1-s4-t7-k2-k1-k2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-boron/263/archives/log.html.gz#s1-s4-t7-k2-k1-k2&lt;/a&gt;&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-boron/263/archives/log.html.gz#s1-s4-t10-k2-k2-k2&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-boron/263/archives/log.html.gz#s1-s4-t10-k2-k2-k2&lt;/a&gt;&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-boron/263/archives/odl3_karaf.log.gz&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-clustering-all-boron/263/archives/odl3_karaf.log.gz&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="39471" author="rudolf.brisuda@pantheon.tech" created="Mon, 24 Oct 2016 13:12:53 +0000"  >&lt;p&gt;No longer relevant due to rewriting netconf topology clustering. If problem persists then this bug has different cause and it is not useful. There should be created new bug with proper state.&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>6067</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=6067]]></customfieldvalue>

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

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

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