<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:14:56 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-406] ietf-netconf-monitoring capability with deviation</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-406</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;We are supporting ietf-netconf-monitoring YANG model but partially, so now we need to advertise the deviation module&lt;br/&gt;
in the netconf server capability.&lt;br/&gt;
I tried doing it like&lt;br/&gt;
&amp;lt;capability&amp;gt;&lt;br/&gt;
     urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?module=ietf-netconf-monitoring&amp;amp;deviations=jnx-ietf-netconf-monitoring-dev&lt;br/&gt;
&amp;lt;/capability&amp;gt;&lt;br/&gt;
&amp;lt;capability&amp;gt;&lt;br/&gt;
    &lt;a href=&quot;http://yang.juniper.net/yang/1.1/jrpc/jnx-ietf-netconf-monitoring-dev/junos/17.3?module=jnx-ietf-netconf-monitoring-dev&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://yang.juniper.net/yang/1.1/jrpc/jnx-ietf-netconf-monitoring-dev/junos/17.3?module=jnx-ietf-netconf-monitoring-dev&lt;/a&gt;&lt;br/&gt;
&amp;lt;/capability&amp;gt;&lt;/p&gt;

&lt;p&gt;but it seems OpenDaylight controller is not taking it as valid capability. &lt;br/&gt;
I posted this question on netmod.org mailing list and Andy Bierman confirmed that this is syntactically correct.&lt;/p&gt;

&lt;p&gt;Am i missing something here ?&lt;/p&gt;



&lt;p&gt;Logs:&lt;br/&gt;
====&lt;br/&gt;
2017-04-21 10:46:29,243 | DEBUG | upCloseable-3-21 | AbstractNetconfSessionNegotiator | 98 - org.opendaylight.netconf.netty-util - 1.1.1.Boron-SR1 | Changingstate from : OPEN_WAIT to : ESTABLISHED for channel: &lt;span class=&quot;error&quot;&gt;&amp;#91;id: 0xce8cf541&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;2017-04-21 10:46:29,243 | DEBUG | upCloseable-3-21 | AbstractNetconfSession           | 98 - org.opendaylight.netconf.netty-util - 1.1.1.Boron-SR1 | Session 73366 created&lt;/p&gt;

&lt;p&gt;2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | NetconfClientSession             | 261 - org.opendaylight.netconf.client - 1.1.1.Boron-SR1 | Client Session NetconfClientSession&lt;/p&gt;
{sessionId=73366, channel=[id: 0xce8cf541]}
&lt;p&gt; created&lt;/p&gt;

&lt;p&gt;2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | NetconfClientSessionNegotiator   | 261 - org.opendaylight.netconf.client - 1.1.1.Boron-SR1 | Netconf session NetconfClientSession&lt;/p&gt;
{sessionId=73366, channel=[id: 0xce8cf541]}
&lt;p&gt; isn&apos;t capable of using exi.&lt;/p&gt;

&lt;p&gt;2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | AbstractNetconfSession           | 98 - org.opendaylight.netconf.netty-util - 1.1.1.Boron-SR1 | SessionNetconfClientSession&lt;/p&gt;
{sessionId=73366, channel=[id: 0xce8cf541]}
&lt;p&gt; up&lt;/p&gt;

&lt;p&gt;2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | NetconfDeviceCommunicator        | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice&lt;/p&gt;
{bag3r_vmx}: Session established&lt;br/&gt;
&lt;br/&gt;
2017-04-21 10:46:29,244 | TRACE | upCloseable-3-21 | NetconfDeviceCommunicator        | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice{bag3r_vmx}
&lt;p&gt;: Session advertised capabilities: NetconfSessionPreferences&lt;/p&gt;
{capabilities=[http://xml.juniper.net/dmi/system/1.0, urn:ietf:params:netconf:capability:url:1.0?protocol=http,ftp,file, urn:ietf:params:xml:ns:netconf:capability:candidate:1.0, urn:ietf:params:netconf:capability:confirmed-commit:1.0, http://xml.juniper.net/netconf/junos/1.0, urn:ietf:params:xml:ns:netconf:capability:validate:1.0, urn:ietf:params:netconf:base:1.0, urn:ietf:params:xml:ns:netconf:base:1.0, urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file,urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0, urn:ietf:params:netconf:capability:validate:1.0, urn:ietf:params:netconf:capability:candidate:1.0], moduleBasedCapabilities=[(http://yang.juniper.net/yang/1.1/jrpc/jnx-ietf-netconf-monitoring-dev/junos/17.3)jnx-ietf-netconf-monitoring-dev, (urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring)ietf-netconf-monitoring], rollback=false, monitoring=false, candidate=true, writableRunning=false}

&lt;p&gt;2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | NetconfDevice                    | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice&lt;/p&gt;
{bag3r_vmx}: Session to remote device established with NetconfSessionPreferences{capabilities=[http://xml.juniper.net/dmi/system/1.0, urn:ietf:params:netconf:capability:url:1.0?protocol=http,ftp,file, urn:ietf:params:xml:ns:netconf:capability:candidate:1.0, urn:ietf:params:netconf:capability:confirmed-commit:1.0, http://xml.juniper.net/netconf/junos/1.0, urn:ietf:params:xml:ns:netconf:capability:validate:1.0, urn:ietf:params:netconf:base:1.0, urn:ietf:params:xml:ns:netconf:base:1.0, urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file, urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0, urn:ietf:params:netconf:capability:validate:1.0, urn:ietf:params:netconf:capability:candidate:1.0], moduleBasedCapabilities=[(http://yang.juniper.net/yang/1.1/jrpc/jnx-ietf-netconf-monitoring-dev/junos/17.3)jnx-ietf-netconf-monitoring-dev, (urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring)ietf-netconf-monitoring], rollback=false, monitoring=false, candidate=true, writableRunning=false}&lt;br/&gt;
&lt;br/&gt;
2017-04-21 10:46:29,244 | DEBUG | upCloseable-3-21 | RemoteDeviceConnectorImpl        | 267 - org.opendaylight.netconf.topology-singleton - 1.1.1.Boron-SR1 |RemoteDevice{bag3r_vmx}
&lt;p&gt;: Connector started successfully&lt;/p&gt;

&lt;p&gt;2017-04-21 10:46:29,244 | DEBUG | ssing-executor-2 | NetconfDevice                    | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice&lt;/p&gt;
{bag3r_vmx}: Schemas exposed by ietf-netconf-monitoring: []&lt;br/&gt;
&lt;br/&gt;
2017-04-21 10:46:29,245 | WARN  | ssing-executor-2 | NetconfDevice                    | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice{bag3r_vmx}
&lt;p&gt;: Netconf device does not provide all yang models reported in hello message capabilities, required but not provided: &lt;span class=&quot;error&quot;&gt;&amp;#91;(http://yang.juniper.net/yang/1.1/jrpc/jnx-ietf-netconf-monitoring-dev/junos/17.3)jnx-ietf-netconf-monitoring-dev, (urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring)ietf-netconf-monitoring&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;2017-04-21 10:46:29,245 | WARN  | ssing-executor-2 | NetconfDevice                    | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice&lt;/p&gt;
{bag3r_vmx}: Attempting to build schema context from required sources&lt;br/&gt;
&lt;br/&gt;
2017-04-21 10:46:29,246 | ERROR | ssing-executor-2 | NetconfDevice                    | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1 | RemoteDevice{bag3r_vmx}
&lt;p&gt;: Initialization in sal failed, disconnecting from devicejava.lang.IllegalStateException: RemoteDevice&lt;/p&gt;
{bag3r_vmx}
&lt;p&gt;: No more sources for schema context&lt;/p&gt;

&lt;p&gt;        at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.setUpSchema(NetconfDevice.java:479)&lt;span class=&quot;error&quot;&gt;&amp;#91;263:org.opendaylight.netconf.sal-netconf-connector:1.4.1.Boron-SR1&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;        at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.run(NetconfDevice.java:428)&lt;span class=&quot;error&quot;&gt;&amp;#91;263:org.opendaylight.netconf.sal-netconf-connector:1.4.1.Boron-SR1&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)&lt;span class=&quot;error&quot;&gt;&amp;#91;:1.8.0_121&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;        at java.util.concurrent.FutureTask.run(FutureTask.java:266)&lt;span class=&quot;error&quot;&gt;&amp;#91;:1.8.0_121&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)&lt;span class=&quot;error&quot;&gt;&amp;#91;:1.8.0_121&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;        at java.util.concurrent.FutureTask.run(FutureTask.java:266)&lt;span class=&quot;error&quot;&gt;&amp;#91;:1.8.0_121&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)&lt;span class=&quot;error&quot;&gt;&amp;#91;:1.8.0_121&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)&lt;span class=&quot;error&quot;&gt;&amp;#91;:1.8.0_121&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)&lt;span class=&quot;error&quot;&gt;&amp;#91;:1.8.0_121&amp;#93;&lt;/span&gt;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21419">NETCONF-406</key>
            <summary>ietf-netconf-monitoring capability with deviation</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="-1">Unassigned</assignee>
                                    <reporter username="dhirutrivedi@gmail.com">Dhirendra Kumar Trivedi</reporter>
                        <labels>
                    </labels>
                <created>Mon, 24 Apr 2017 10:10:37 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:40 +0000</updated>
                            <resolved>Tue, 28 Aug 2018 00:09:32 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="40017" author="tcere" created="Mon, 24 Apr 2017 14:25:19 +0000"  >&lt;p&gt;Deviations were added to yangtools in carbon and are not yet supported on netconf side.&lt;/p&gt;</comment>
                            <comment id="40018" author="rovarga" created="Mon, 24 Apr 2017 15:35:13 +0000"  >&lt;p&gt;Actually the problem seems to be that jnx-ietf-netconf-monitoring-dev is not advertized via netconf-monitoring and hence we do not have a source for that model &amp;#8211; pre-populating it to the model cache may help.&lt;/p&gt;</comment>
                            <comment id="40019" author="rovarga" created="Tue, 2 May 2017 08:59:12 +0000"  >&lt;p&gt;Has providing the module helped? If not, can you provide karaf.log files from the failed connection attempt.&lt;/p&gt;</comment>
                            <comment id="64809" author="rovarga" created="Tue, 28 Aug 2018 00:09:32 +0000"  >&lt;p&gt;15+ months without a response, closing this issue.&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>8279</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=8279]]></customfieldvalue>

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

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