<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:53:44 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>[CONTROLLER-730] Issue in rpc call on mounted schema</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-730</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;While making rpc call on mounted schema ODL tries to find the provided rpc in available schema and&lt;br/&gt;
according to current scenario &lt;br/&gt;
1. ODL tries to find the qname for the given module and node name from global schema (which has schemas for local netconf sever) instead of mounted schema.&lt;/p&gt;

&lt;p&gt;2. ODL tries to lookup for the remote rpc into the global schema which has only module belong to local netconf server instead of mounted point schema&lt;br/&gt;
due to which it returns validName and rpcDefinition as null.&lt;/p&gt;

&lt;p&gt;both of above scnearios should be corrected for successful rpc call on mounted schema.&lt;br/&gt;
onGlobalContextUpdated method need to updated in a way that it adds the mounted schema to the map of already available schemas so that rpc calls of both the server(local and mounted schema) can work fine.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Linux&lt;br/&gt;
Platform: PC&lt;/p&gt;</environment>
        <key id="25284">CONTROLLER-730</key>
            <summary>Issue in rpc call on mounted schema</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="jgloncak">Jozef Gloncak</assignee>
                                    <reporter username="ankit21.a@tcs.com">Ankit agarwal</reporter>
                        <labels>
                    </labels>
                <created>Tue, 26 Aug 2014 10:54:31 +0000</created>
                <updated>Tue, 25 Jul 2023 08:24:07 +0000</updated>
                            <resolved>Tue, 9 Sep 2014 08:30:46 +0000</resolved>
                                                                    <component>restconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                                                                <comments>
                            <comment id="48965" author="tony.tkacik@gmail.com" created="Wed, 27 Aug 2014 09:33:16 +0000"  >&lt;p&gt;Could you provide example how are you trying to invoke mounted RPC?&lt;/p&gt;</comment>
                            <comment id="48966" author="ankit21.a@tcs.com" created="Wed, 27 Aug 2014 10:18:11 +0000"  >&lt;p&gt;Hi Tony,&lt;/p&gt;

&lt;p&gt;I am using following url to make rpc call,&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://localhost:8080/restconf/operations/opendaylight-inventory:nodes/node/m10schemanew/yang-ext:mount/configuration:get-system-information&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8080/restconf/operations/opendaylight-inventory:nodes/node/m10schemanew/yang-ext:mount/configuration:get-system-information&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="48967" author="ankit21.a@tcs.com" created="Tue, 2 Sep 2014 05:03:31 +0000"  >&lt;p&gt;Hi Tony,&lt;/p&gt;

&lt;p&gt;Is there any update on this?&lt;br/&gt;
If you think a change is required in ODL then please acknowledge it.&lt;/p&gt;</comment>
                            <comment id="48968" author="jgloncak" created="Tue, 9 Sep 2014 05:46:35 +0000"  >&lt;p&gt;I passed via code which handle invoking of rpc.&lt;br/&gt;
Firstly there is method invokeRpc() which contains resolveIdentifierInInvokeRpc(). This method returns rpc executor where concrete rpc is searched in:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;schema context of running ODL if mount point doesn&apos;t exist&lt;/li&gt;
	&lt;li&gt;schema context of device behind mount point if MP exists.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Everytime the rpc in front or behind mount point is called the executor is created as mentioned.&lt;/p&gt;


&lt;p&gt;If rpc is called via your URI&lt;br/&gt;
&lt;a href=&quot;http://localhost:8080/restconf/operations/opendaylight-inventory:nodes/node/m10schemanew/yang-ext:mount/configuration:get-system-information&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8080/restconf/operations/opendaylight-inventory:nodes/node/m10schemanew/yang-ext:mount/configuration:get-system-information&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;then rpc &amp;gt;get-system-information&amp;lt; from module &amp;gt;configuration&amp;lt; from schema context BEHIND mount point is called.&lt;/p&gt;


&lt;p&gt;You mentioned in numbering 1. that for mounted device ODL tries to find rpc from global schema which isn&apos;t true. Rpc is searched in schema context of mount point (RestconfImpl.java row 545 - findRpc() method).&lt;/p&gt;

&lt;p&gt;I wasn&apos;t able to understand numbering 2. but I think that it is the same (or very simillar) as numbering 1.&lt;/p&gt;

&lt;p&gt;Currently I can&apos;t see your problem. Could you specify concrete example. What version of ODL are you using? &lt;/p&gt;

&lt;p&gt;The feature of distinguising between infront and behind mount point rpc calling was added 7 week ago with commit 987da65... - &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-633&quot; title=&quot;RESTCONF support RPC on yang-ext:mount for any mounted &amp;quot;module&amp;quot;&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-633&quot;&gt;&lt;del&gt;CONTROLLER-633&lt;/del&gt;&lt;/a&gt; - rpcs behind yang-ext:mount aren&apos;t always executed.&lt;/p&gt;</comment>
                            <comment id="48969" author="ankit21.a@tcs.com" created="Tue, 9 Sep 2014 06:51:26 +0000"  >
&lt;p&gt;Hi,&lt;br/&gt;
Thanks for your time,&lt;/p&gt;

&lt;p&gt;Firstly i would like to explain what i was asking for&lt;/p&gt;

&lt;p&gt;#1: I meant that when ODL tries to find rpc in schema context ,&lt;br/&gt;
it was looking into the globalschema instead of schema context of mount point.&lt;/p&gt;

&lt;p&gt;Now with latest clone of ODL of 05 Sep, it is working fine.&lt;/p&gt;

&lt;p&gt;#2: query in first point and second point is alomost same.&lt;br/&gt;
which is Anywaays is working fine so we can move and close this Bug.&lt;/p&gt;

&lt;p&gt;May be what you have said is right and merge of &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-633&quot; title=&quot;RESTCONF support RPC on yang-ext:mount for any mounted &amp;quot;module&amp;quot;&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-633&quot;&gt;&lt;del&gt;CONTROLLER-633&lt;/del&gt;&lt;/a&gt; resolves this issue.&lt;/p&gt;


&lt;p&gt;Thanks for your time and investiagtion.&lt;/p&gt;</comment>
                            <comment id="48970" author="jgloncak" created="Tue, 9 Sep 2014 08:30:46 +0000"  >&lt;p&gt;Reported problem was solved under &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-633&quot; title=&quot;RESTCONF support RPC on yang-ext:mount for any mounted &amp;quot;module&amp;quot;&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-633&quot;&gt;&lt;del&gt;CONTROLLER-633&lt;/del&gt;&lt;/a&gt;&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>1620</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=1620]]></customfieldvalue>

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10202" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Priority</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10313"><![CDATA[Highest]]></customfieldvalue>

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

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