<!-- 
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-224] Netconf session closes and reconnects on error from non-heart beat RPC</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-224</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;NETCONF session closes on rpc error for non-heatbeat transaction. The desired behavoir is for the session to stay up and an error returned to the application (in this case it was a RESTconf initiated PUT (lock before edit-config).&lt;/p&gt;

&lt;p&gt;Here is the log entry for the lock that failed. The failed lock was due to a mis-configuration on the device side wrt write transactions but get-config and other read only transactions were working fine before this error.&lt;/p&gt;


&lt;p&gt;2016-06-28 21:59:10,858 | TRACE | oupCloseable-7-1 | NetconfDeviceCommunicator        | RemoteDevice&lt;/p&gt;
{ncs5502}: Matched request: &amp;lt;rpc message-id=&quot;m-1&quot; xmlns=&quot;urn:ietf:params:xml:ns:netconf:base:1.0&quot;&amp;gt;&lt;br/&gt;
&amp;lt;lock&amp;gt;&lt;br/&gt;
&amp;lt;target&amp;gt;&lt;br/&gt;
&amp;lt;candidate/&amp;gt;&lt;br/&gt;
&amp;lt;/target&amp;gt;&lt;br/&gt;
&amp;lt;/lock&amp;gt;&lt;br/&gt;
&amp;lt;/rpc&amp;gt;&lt;br/&gt;
to response: &amp;lt;rpc-reply xmlns=&quot;urn:ietf:params:xml:ns:netconf:base:1.0&quot; message-id=&quot;m-1&quot;&amp;gt;&lt;br/&gt;
&amp;lt;rpc-error&amp;gt;&lt;br/&gt;
  &amp;lt;error-type&amp;gt;application&amp;lt;/error-type&amp;gt;&lt;br/&gt;
  &amp;lt;error-tag&amp;gt;operation-failed&amp;lt;/error-tag&amp;gt;&lt;br/&gt;
  &amp;lt;error-severity&amp;gt;error&amp;lt;/error-severity&amp;gt;&lt;br/&gt;
  &amp;lt;error-message xml:lang=&quot;en&quot;&amp;gt;ME_BACKEND_ERROR_UNAUTHORIZED &lt;span class=&quot;error&quot;&gt;&amp;#91;non-QT backend request failed&amp;#93;&lt;/span&gt;&amp;lt;/error-message&amp;gt;&lt;br/&gt;
&amp;lt;/rpc-error&amp;gt;&lt;br/&gt;
&amp;lt;rpc-error&amp;gt;&lt;br/&gt;
  &amp;lt;error-type&amp;gt;application&amp;lt;/error-type&amp;gt;&lt;br/&gt;
  &amp;lt;error-tag&amp;gt;backend-status-summary&amp;lt;/error-tag&amp;gt;&lt;br/&gt;
  &amp;lt;error-severity&amp;gt;warning&amp;lt;/error-severity&amp;gt;&lt;br/&gt;
  &amp;lt;error-message xml:lang=&quot;en&quot;&amp;gt;QT/SysDB backend passed, non-QT backend failed &lt;span class=&quot;error&quot;&gt;&amp;#91;read rest of response for details&amp;#93;&lt;/span&gt;&amp;lt;/error-message&amp;gt;&lt;br/&gt;
&amp;lt;/rpc-error&amp;gt;&lt;br/&gt;
&amp;lt;/rpc-reply&amp;gt;&lt;br/&gt;
&lt;br/&gt;
2016-06-28 21:59:10,860 | WARN  | oupCloseable-7-1 | KeepaliveSalFacade               | RemoteDevice{ncs5502}
&lt;p&gt;: Rpc failure detected. Reconnecting netconf session&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21237">NETCONF-224</key>
            <summary>Netconf session closes and reconnects on error from non-heart beat RPC</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="jmorvay@cisco.com">Jakub Morvay</assignee>
                                    <reporter username="bf1936@att.com">Brian Freeman</reporter>
                        <labels>
                    </labels>
                <created>Mon, 4 Jul 2016 14:31:08 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:26 +0000</updated>
                            <resolved>Tue, 19 Jul 2016 18:29:48 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="39480" author="jmorvay@cisco.com" created="Tue, 12 Jul 2016 09:07:20 +0000"  >&lt;p&gt;Hi Brian,&lt;/p&gt;

&lt;p&gt;I tried to reproduce this bug but I wasn&apos;t able to. Simulated with netconf test tool modified to return error, when processing lock request. &lt;/p&gt;

&lt;p&gt;But keep alive mechanism didn&apos;t drop the session. Actually when looking through implementation, reconnect should be triggered only when RPC fails to reach device, response is not received etc.. But any rpc response, even with rpc error should be fine.&lt;/p&gt;

&lt;p&gt;If possible, can you please send karaf log. Or you can try to configure device without keep alive mechanism and send some rpcs to device after unsuccessful lock.&lt;/p&gt;</comment>
                            <comment id="39481" author="bf1936@att.com" created="Tue, 19 Jul 2016 18:29:48 +0000"  >&lt;p&gt;I just tried to recreate it as well on Beryllium SR2 and could not. I suspect the first iterations of the interface with the device were flaky. If this re-occurs I will re-open the report. Sorry for false alarm.&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>6153</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=6153]]></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_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10332"><![CDATA[Boron-RC0]]></customfieldvalue>

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

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