<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:15:43 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-719] NETCONF operation failed message - Caused by: org.opendaylight.mdsal.common.api.ReadFailedException: NETCONF operation failed</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-719</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;I have PUT a NETCONF device (Junos vMX r18.2) on ODL (Magnesium stable version) using the following Postman command&lt;/p&gt;

&lt;p&gt;PUT http://&amp;lt;MY_CONTROLLER&amp;gt;:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/VMX-1&lt;/p&gt;

&lt;p&gt;&#160;&lt;br/&gt;
&amp;lt;node&#160;xmlns=&quot;urn:TBD:params:xml:ns:yang:network-topology&quot;&amp;gt;&#160;&lt;br/&gt;
&amp;lt;node-id&amp;gt;VMX-1&amp;lt;/node-id&amp;gt;&#160;&lt;br/&gt;
&amp;lt;host&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;&amp;lt;Device-IP&amp;gt;&amp;lt;/host&amp;gt;&#160;&lt;br/&gt;
&amp;lt;port&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;22&amp;lt;/port&amp;gt;&#160;&lt;br/&gt;
&amp;lt;username&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;admin&amp;lt;/username&amp;gt;&#160;&lt;br/&gt;
&amp;lt;password&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;admin&amp;lt;/password&amp;gt;&#160;&lt;br/&gt;
&amp;lt;tcp-only&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;false&amp;lt;/tcp-only&amp;gt;&#160;&lt;br/&gt;
&amp;lt;schema-cache-directory&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;VMX-2_device_cache&amp;lt;/schema-cache-directory&amp;gt;&#160;&lt;br/&gt;
&amp;lt;reconnect-on-changed-schema&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;true&amp;lt;/reconnect-on-changed-schema&amp;gt;&#160;&lt;br/&gt;
&amp;lt;connection-timeout-millis&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;20000&amp;lt;/connection-timeout-millis&amp;gt;&#160;&lt;br/&gt;
&amp;lt;default-request-timeout-millis&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;60000&amp;lt;/default-request-timeout-millis&amp;gt;&#160;&lt;br/&gt;
&amp;lt;max-connection-attempts&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;0&amp;lt;/max-connection-attempts&amp;gt;&#160;&lt;br/&gt;
&amp;lt;between-attempts-timeout-millis&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;2000&amp;lt;/between-attempts-timeout-millis&amp;gt;&#160;&lt;br/&gt;
&amp;lt;sleep-factor&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;1.5&amp;lt;/sleep-factor&amp;gt;&#160;&lt;br/&gt;
&amp;lt;keepalive-delay&#160;xmlns=&quot;urn:opendaylight:netconf-node-topology&quot;&amp;gt;120&amp;lt;/keepalive-delay&amp;gt;&#160;&lt;br/&gt;
&amp;lt;/node&amp;gt;&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
The device is created ok and I can query the config and operational state&lt;br/&gt;
&#160;&lt;br/&gt;
GET &lt;a href=&quot;http://192.168.15.205:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/VMX-1/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://&amp;lt;MY_CONTROLLER&amp;gt;:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/VMX-1/&lt;/a&gt;&lt;br/&gt;
&#160;&lt;br/&gt;
However, when I attempt to retrieve all its capabilities which are available through the mount point using ...&lt;br/&gt;
&#160;&lt;br/&gt;
&lt;a href=&quot;http://192.168.15.205:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/VMX-1/yang-ext:mount&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://&amp;lt;MY_CONTROLLER&amp;gt;:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/VMX-1/yang-ext:mount&lt;/a&gt;&lt;br/&gt;
&#160;&lt;br/&gt;
I receive the following reply&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
{&lt;br/&gt;
&#160;&#160;&#160;&#160;&quot;errors&quot;:&#160;{&lt;br/&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&quot;error&quot;:&#160;[&lt;br/&gt;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&lt;/p&gt;
{
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&quot;error-type&quot;:&#160;&quot;application&quot;,
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&quot;error-tag&quot;:&#160;&quot;operation-failed&quot;,
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&quot;error-message&quot;:&#160;&quot;NETCONF&#160;operation&#160;failed&quot;
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;}
&lt;p&gt;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;]&lt;br/&gt;
&#160;&#160;&#160;&#160;}&lt;br/&gt;
}&lt;br/&gt;
Looking&#160; at the controller log I see exceptions ...&lt;br/&gt;
&#160;&lt;br/&gt;
Error reading / from datastore CONFIGURATION&lt;br/&gt;
java.util.concurrent.ExecutionException: ReadFailedException{message=NETCONF operation failed, errorList=[RpcError &lt;span class=&quot;error&quot;&gt;&amp;#91;message=NETCONF operation failed, severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=java.lang.UnsupportedOperationException&amp;#93;&lt;/span&gt;]}&lt;br/&gt;
 at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:553) ~&lt;span class=&quot;error&quot;&gt;&amp;#91;bundleFile:?&amp;#93;&lt;/span&gt;&lt;br/&gt;
&#160;&lt;br/&gt;
etc&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
and&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
Caused by: org.opendaylight.mdsal.common.api.ReadFailedException: NETCONF operation failed&lt;br/&gt;
 at org.opendaylight.netconf.sal.connect.netconf.sal.tx.ReadOnlyTx$1.onFailure(ReadOnlyTx.java:64) ~&lt;span class=&quot;error&quot;&gt;&amp;#91;?:?&amp;#93;&lt;/span&gt;&lt;br/&gt;
 at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1064) ~&lt;span class=&quot;error&quot;&gt;&amp;#91;bundleFile:?&amp;#93;&lt;/span&gt;&lt;br/&gt;
&#160;&lt;br/&gt;
...&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
My controller is installed on Cento7 and build with java11&lt;br/&gt;
&#160;&lt;br/&gt;
I&apos;m following instructions given in the cookbook&lt;br/&gt;
&lt;a href=&quot;https://subscription.packtpub.com/book/virtualization_and_cloud/9781786462305/1/ch01lvl1sec11/mounting-a-netconf-device&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://subscription.packtpub.com/book/virtualization_and_cloud/9781786462305/1/ch01lvl1sec11/mounting-a-netconf-device&lt;/a&gt;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
Is this an issue with what the device is returning ? I can see on the device log its returning the full configuration, but the ODL is failing to read it&#160;&lt;br/&gt;
I&apos;ve tried various release of ODL&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;br/&gt;
&#160;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Centos 7 VM&lt;/p&gt;

&lt;p&gt;Java11 jre&lt;/p&gt;

&lt;p&gt;remotes/origin/stable/magnesium&lt;/p&gt;</environment>
        <key id="33175">NETCONF-719</key>
            <summary>NETCONF operation failed message - Caused by: org.opendaylight.mdsal.common.api.ReadFailedException: NETCONF operation failed</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <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="jluhrsen">Jamo Luhrsen</assignee>
                                    <reporter username="john.mangan22">John Mangan</reporter>
                        <labels>
                            <label>netconf</label>
                    </labels>
                <created>Wed, 19 Aug 2020 16:25:40 +0000</created>
                <updated>Wed, 30 Sep 2020 09:20:18 +0000</updated>
                            <resolved>Wed, 30 Sep 2020 09:20:18 +0000</resolved>
                                    <version>Magnesium SR1</version>
                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="68652" author="JIRAUSER13124" created="Wed, 30 Sep 2020 09:19:44 +0000"  >&lt;p&gt;This issue is a consequence of the junos device not revealing its yang schemas during the capabilities exchange.&#160;&lt;/p&gt;

&lt;p&gt;This reports can be closed&#160;&#160;&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="15803" name="odl-get-mounted-device-config-stack-trace.txt" size="23336" author="john.mangan22" created="Thu, 20 Aug 2020 13:30:05 +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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03uhr:</customfieldvalue>

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