<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:15:46 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-734] The submodule rpc is not working as expected.</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-734</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;I&apos;ve trying to implement rpc statement in submodule and included from module for separation of concerns purpose, and both &quot;sysrepo&quot; and &quot;pyang&quot; are able to interpret it correctly, which is directly bind the rpc statement under the main module.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;However, when the data comes to ODL it triggers the following error:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
2020-10-12T19:45:36,116 | INFO | nioEventLoopGroupCloseable-3-1 | StreamWriterFacade | 317 - org.opendaylight.yangtools.yang-data-codec-xml - 4.0.13 | Encountered annotation message-id not bound to module. Please examine the call stack and fix &lt;span class=&quot;code-keyword&quot;&gt;this&lt;/span&gt; warning by defining a proper YANG annotation to cover it

2020-10-12T19:45:36,525 | WARN  | remote-connector-processing-executor-11 | NetconfDevice                    | 287 - org.opendaylight.netconf.sal-netconf-connector - 1.11.2 | RemoteDevice{ark85}: Unable to build schema context, unsatisfied imports {RevisionSourceIdentifier [name=bytedance-dns@2020-10-13]=[ModuleImportImpl [name=bytedance-dns-rpc, revision=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;, semanticVersion=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;]]}, will reattempt with resolved only
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;from my perspective, the message-id is referring to the message-id for rpc message, that is to say it&apos;s failed to be bound to the main module for some reason, I&apos;m wondering if there&apos;s any way to solve this issue?&lt;/p&gt;

&lt;p&gt;The attachment is the yang model corresponding to this issue.&lt;/p&gt;

&lt;p&gt;The Yang Tool Version that I use is 4.0.13.&lt;/p&gt;</description>
                <environment></environment>
        <key id="33400">NETCONF-734</key>
            <summary>The submodule rpc is not working as expected.</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="10003">Cannot Reproduce</resolution>
                                        <assignee username="ivanm1996">Ivan Martiniak</assignee>
                                    <reporter username="libraskywalker">Wanxin Cai</reporter>
                        <labels>
                    </labels>
                <created>Tue, 13 Oct 2020 18:12:07 +0000</created>
                <updated>Tue, 1 Feb 2022 19:04:42 +0000</updated>
                            <resolved>Tue, 1 Feb 2022 19:04:21 +0000</resolved>
                                    <version>Magnesium SR2</version>
                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="68713" author="rovarga" created="Sun, 18 Oct 2020 19:47:32 +0000"  >&lt;p&gt;So this is a module and a submodule, and yes, it would seem that &apos;bytedance-dns-rpc&apos; is missing. This is not a general yangtools issue, as it can properly resolve the two if they are being fed into it.&lt;/p&gt;

&lt;p&gt;I suspect this is either a problem with the device (i.e. announced sources, etc.) or NETCONF.&lt;/p&gt;</comment>
                            <comment id="68714" author="rovarga" created="Sun, 18 Oct 2020 19:48:29 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=libraskywalker&quot; class=&quot;user-hover&quot; rel=&quot;libraskywalker&quot;&gt;libraskywalker&lt;/a&gt; can you post some information about the SB device you are connecting to?&lt;/p&gt;</comment>
                            <comment id="68715" author="rovarga" created="Sun, 18 Oct 2020 19:49:53 +0000"  >&lt;p&gt;Specifically I think we need:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;netconf capabilities it reports&lt;/li&gt;
	&lt;li&gt;the content of ietf-netconf-monitoring (if implemented)&lt;/li&gt;
	&lt;li&gt;yang-library content (if implemented)&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&#160;&lt;/p&gt;</comment>
                            <comment id="68807" author="JIRAUSER13229" created="Wed, 16 Dec 2020 00:40:10 +0000"  >&lt;p&gt;encounter same problem I think,&#160; I&apos;m trying to integrating FRR which also use submodule and include in it&apos;s frr-bgp.yang, same error was triggered as below:&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;2020-12-15T20:04:14,878 | WARN &#160;| remote-connector-processing-executor-11 | NetconfDevice &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;| 287 - org.opendaylight.netconf.sal-netconf-connector - 1.11.2 | RemoteDevice{ark102}: Netconf device provides additional yang models not reported in hello message capabilities: [(http:&lt;span class=&quot;code-comment&quot;&gt;//frrouting.org/yang/route-types?revision=2018-03-28)frr-route-types, (urn:ietf:params:xml:ns:yang:ietf-yang-library?revision=2019-01-04)ietf-yang-library, (urn:ietf:params:xml:ns:yang:ietf-crypto-types?revision=2019-07-02)ietf-crypto-types, (urn:ietf:params:xml:ns:yang:ietf-tcp-server?revision=2019-07-02)ietf-tcp-server, (http://frrouting.org/yang/bgp-types?revision=2019-12-03)frr-bgp-types, (urn:ietf:params:xml:ns:yang:ietf-bgp-types?revision=2019-10-03)ietf-bgp-types, (urn:ietf:params:xml:ns:yang:ietf-tcp-common?revision=2019-07-02)ietf-tcp-common, (urn:ietf:params:xml:ns:yang:ietf-ssh-server?revision=2019-07-02)ietf-ssh-server, (http://frrouting.org/yang/eigrpd?revision=2019-09-09)frr-eigrpd, (urn:ietf:params:xml:ns:yang:ietf-netconf-server?revision=2019-07-02)ietf-netconf-server, (urn:ietf:params:xml:ns:yang:ietf-tls-common?revision=2019-07-02)ietf-tls-common, (http://frrouting.org/yang/isisd?revision=2020-04-06)frr-isisd, (urn:ietf:params:xml:ns:yang:ietf-interfaces?revision=2018-02-20)ietf-interfaces, (urn:ietf:params:xml:ns:yang:ietf-ssh-common?revision=2019-07-02)ietf-ssh-common, (http://frrouting.org/yang/bfdd?revision=2019-05-09)frr-bfdd, (http://www.sysrepo.org/yang/sysrepo-monitoring?revision=2020-04-17)sysrepo-monitoring, (http://frrouting.org/yang/frr-deviations-bgp-datacenter?revision=2019-12-03)frr-deviations-bgp-datacenter, (urn:ietf:params:xml:ns:yang:ietf-datastores?revision=2018-02-14)ietf-datastores, (http://www.sysrepo.org/yang/sysrepo?revision=2020-01-15)sysrepo, (http://frrouting.org/yang/routing?revision=2019-08-15)frr-routing, (urn:ietf:params:xml:ns:yang:ietf-tls-server?revision=2019-07-02)ietf-tls-server, (urn:ietf:params:xml:ns:yang:ietf-netconf-nmda?revision=2019-01-07)ietf-netconf-nmda, (http://frrouting.org/yang/igmp?revision=2019-11-06)frr-igmp, (http://frrouting.org/yang/route-map?revision=2019-07-01)frr-route-map, (urn:ietf:params:xml:ns:yang:ietf-truststore?revision=2019-07-02)ietf-truststore, (urn:ietf:params:xml:ns:yang:ietf-tcp-client?revision=2019-07-02)ietf-tcp-client, (http://frrouting.org/yang/&lt;span class=&quot;code-keyword&quot;&gt;interface&lt;/span&gt;?revision=2020-02-05)frr-&lt;span class=&quot;code-keyword&quot;&gt;interface&lt;/span&gt;, (urn:ietf:params:xml:ns:yang:ietf-keystore?revision=2019-07-02)ietf-keystore, (http://frrouting.org/yang/vrf?revision=2019-12-06)frr-vrf, (http://frrouting.org/yang/filter?revision=2019-07-04)frr-filter, (http://frrouting.org/yang/bgp?revision=2019-12-03)frr-bgp, (http://frrouting.org/yang/frr-bgp-rpki?revision=2019-12-03)frr-bgp-rpki, (urn:ietf:params:xml:ns:yang:ietf-origin?revision=2018-02-14)ietf-origin]
&lt;/span&gt;2020-12-15T20:04:14,879 | WARN &#160;| remote-connector-processing-executor-11 | NetconfDevice &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;| 287 - org.opendaylight.netconf.sal-netconf-connector - 1.11.2 | RemoteDevice{ark102}: Adding provided but not required sources as required to prevent failures
2020-12-15T20:04:14,888 | WARN &#160;| remote-connector-processing-executor-1 | NetconfDevice &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160; &#160;| 287 - org.opendaylight.netconf.sal-netconf-connector - 1.11.2 | RemoteDevice{ark102}: Unable to build schema context, unsatisfied imports {RevisionSourceIdentifier [name=frr-bgp@2019-12-03]=[ModuleImportImpl [name=frr-bgp-bmp, revision=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;, semanticVersion=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;], ModuleImportImpl [name=frr-bgp-common, revision=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;, semanticVersion=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;], ModuleImportImpl [name=frr-bgp-neighbor, revision=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;, semanticVersion=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;], ModuleImportImpl [name=frr-bgp-peer-group, revision=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;, semanticVersion=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;], ModuleImportImpl [name=frr-bgp-common-structure, revision=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;, semanticVersion=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;], ModuleImportImpl [name=frr-bgp-common-multiprotocol, revision=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;, semanticVersion=&lt;span class=&quot;code-keyword&quot;&gt;null&lt;/span&gt;]]}, will reattempt with resolved only
&#160;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&#160;&lt;br/&gt;
&#160;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;netconf capabilities it reports like :
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;&amp;lt;unavailable-capabilities xmlns=&lt;span class=&quot;code-quote&quot;&gt;&quot;urn:opendaylight:netconf-node-topology&quot;&lt;/span&gt;&amp;gt; &amp;lt;unavailable-capability&amp;gt; &amp;lt;capability&amp;gt;(http:&lt;span class=&quot;code-comment&quot;&gt;//frrouting.org/yang/bgp?revision=2019-12-03)frr-bgp&amp;lt;/capability&amp;gt; &amp;lt;failure-reason&amp;gt;unable-to-resolve&amp;lt;/failure-reason&amp;gt; &amp;lt;/unavailable-capability&amp;gt; &amp;lt;/unavailable-capabilities&amp;gt; &amp;lt;available-capabilities xmlns=&lt;span class=&quot;code-quote&quot;&gt;&quot;urn:opendaylight:netconf-node-topology&quot;&lt;/span&gt;&amp;gt; .... &amp;lt;available-capability&amp;gt; &amp;lt;capability-origin&amp;gt;device-advertised&amp;lt;/capability-origin&amp;gt; &amp;lt;capability&amp;gt;(urn:ietf:params:xml:ns:yang:1?revision=2017-02-20)yang&amp;lt;/capability&amp;gt; &amp;lt;/available-capability&amp;gt; &amp;lt;available-capability&amp;gt; &amp;lt;capability-origin&amp;gt;device-advertised&amp;lt;/capability-origin&amp;gt; &amp;lt;capability&amp;gt;(urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults?revision=2011-06-01)ietf-netconf-with-defaults&amp;lt;/capability&amp;gt; &amp;lt;/available-capability&amp;gt; &amp;lt;available-capability&amp;gt; &amp;lt;capability&amp;gt;(http://frrouting.org/yang/igmp?revision=2019-11-06)frr-igmp&amp;lt;/capability&amp;gt; &amp;lt;/available-capability&amp;gt; &amp;lt;available-capability&amp;gt; &amp;lt;capability&amp;gt;(http://frrouting.org/yang/eigrpd?revision=2019-09-09)frr-eigrpd&amp;lt;/capability&amp;gt;&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;bgp is in&#160;unavailable-capability but others were in&#160;available-capability&lt;/p&gt;&lt;/li&gt;
	&lt;li&gt;feature:info odl-yanglib : 1.8.2&lt;/li&gt;
	&lt;li&gt;the ietf-netconf-monitoring:&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&amp;lt;available-capability&amp;gt;&lt;br/&gt;
&amp;lt;capability-origin&amp;gt;device-advertised&amp;lt;/capability-origin&amp;gt;&lt;br/&gt;
&amp;lt;capability&amp;gt;(urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?revision=2010-10-04)ietf-netconf-monitoring&amp;lt;/capability&amp;gt;&lt;br/&gt;
&amp;lt;/available-capability&amp;gt; * &#160;I also checked cache/yang and found just parent yang was fetched, without any included submodules. then I manually copy these relative&#160;submodules to cache/yang, but the issue still same; * ODL version:0.12.2&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;OS: ubuntu 18.04.5&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="70505" author="rovarga" created="Tue, 1 Feb 2022 19:04:21 +0000"  >&lt;p&gt;So the primary problem was the second WARNING, as the INFO is mostly harmless.&lt;br/&gt;
Closing this issue as Cannot Reproduce, with &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-856&quot; title=&quot;Integrate message-id and other NETCONF attributes&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-856&quot;&gt;NETCONF-856&lt;/a&gt; tracking the work to get rid of the INFO.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10300">
                    <name>Issue split</name>
                                            <outwardlinks description="split to">
                                        <issuelink>
            <issuekey id="35202">NETCONF-856</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="17204" name="[NETCONF-734] Steps to reproduce.rtf" size="92179" author="ivanm1996" created="Wed, 12 Jan 2022 12:32:03 +0000"/>
                            <attachment id="15900" name="bytedance-dns-rpc.yang" size="232" author="libraskywalker" created="Tue, 13 Oct 2020 18:10:58 +0000"/>
                            <attachment id="15901" name="bytedance-dns.yang" size="184" author="libraskywalker" created="Tue, 13 Oct 2020 18:10:28 +0000"/>
                            <attachment id="17205" name="karaf.log" size="356025" author="ivanm1996" created="Wed, 12 Jan 2022 12:32:03 +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|i03v93:</customfieldvalue>

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