<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:16: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-1134] EMPTY body response on POST to /rests/operations</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-1134</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;There is a bug in odl netconf for network element with custom yang model which contains RPC call.&lt;br/&gt;
When you trying to invoke rpc method via api call like &quot;POST /rests/operations/{yang_module}:{method_name}&quot;, you expecting to receive response with body declared in output region of rpc call in yang model. For example:&lt;/p&gt;

&lt;p&gt;&#160; rpc software-check {&lt;br/&gt;
&#160; &#160; description&lt;br/&gt;
&#160; &#160; &#160; &quot;Install a previously downloaded software package.&quot;;&lt;br/&gt;
&#160; &#160; input&lt;/p&gt;

{ &#160; &#160; &#160; uses check-input; &#160; &#160; }

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

{ &#160; &#160; &#160; uses check-output; &#160; &#160; }

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

&lt;p&gt;Response body have to represent a structure declared in &quot;check-output&quot; grouping, BUT body is EMPTY.&lt;/p&gt;

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

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

&lt;p&gt;Version&#160; ODL: &#160; chlorine-SR1 (0.17.1), phosphorus-SR1 (0.15.1)&lt;/p&gt;</description>
                <environment>&lt;p&gt;Have found it using ONAP London release&lt;/p&gt;</environment>
        <key id="37196">NETCONF-1134</key>
            <summary>EMPTY body response on POST to /rests/operations</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="ivanhrasko">Ivan Hrasko</assignee>
                                    <reporter username="VladislavLH">Vladislav LH</reporter>
                        <labels>
                    </labels>
                <created>Mon, 14 Aug 2023 12:01:13 +0000</created>
                <updated>Wed, 13 Sep 2023 13:03:18 +0000</updated>
                            <resolved>Wed, 13 Sep 2023 13:03:18 +0000</resolved>
                                    <version>6.0.1</version>
                                                    <component>restconf-nb</component>
                    <component>restconf-openapi</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="72512" author="rovarga" created="Wed, 30 Aug 2023 14:33:08 +0000"  >&lt;p&gt;See &lt;a href=&quot;https://www.rfc-editor.org/rfc/rfc8040#section-3.6.1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.rfc-editor.org/rfc/rfc8040#section-3.6.1&lt;/a&gt; &lt;/p&gt;</comment>
                            <comment id="72518" author="JIRAUSER14508" created="Tue, 5 Sep 2023 09:42:29 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=VladislavLH&quot; class=&quot;user-hover&quot; rel=&quot;VladislavLH&quot;&gt;VladislavLH&lt;/a&gt;&#160; can you provide more detailed steps to reproduce for this issue?&lt;/p&gt;

&lt;p&gt;I tested this behavior and everything seems to work fine.&lt;br/&gt;
I used this example test device &lt;a href=&quot;https://github.com/PANTHEONtech/lighty-netconf-simulator/tree/main/examples/devices/lighty-network-topology-device&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/PANTHEONtech/lighty-netconf-simulator/tree/main/examples/devices/lighty-network-topology-device&lt;/a&gt;&lt;br/&gt;
RPCs declared in network-topology-rpcs@2018-03-20.yang works and return output as expected.&lt;br/&gt;
I could not reproduce this issue.&lt;/p&gt;</comment>
                            <comment id="72525" author="JIRAUSER16409" created="Thu, 7 Sep 2023 11:35:58 +0000"  >&lt;p&gt;Hi Samuel,&lt;/p&gt;

&lt;p&gt;I&apos;ll give you a hint, we&apos;ve already find the source of the problem. It is here in file netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/sal/NetconfDeviceRpc.java&lt;/p&gt;

&lt;p&gt;invokeRpc function returns value before rpc completion, which cause that DOMRpcResult.getResult() is empty and response has empty body&lt;/p&gt;</comment>
                            <comment id="72526" author="JIRAUSER16409" created="Thu, 7 Sep 2023 11:55:22 +0000"  >&lt;p&gt;and when the delegate is completed and future callback invokes onSuccess method there are no requests waiting for response because response is already handled with empty DOMRpcResult&#160;&lt;/p&gt;</comment>
                            <comment id="72537" author="ivanhrasko" created="Wed, 13 Sep 2023 13:02:59 +0000"  >&lt;p&gt;We are not aligned with your analysis. Please provide exact steps to reproduce, paths, payloads, model. Otherwise we are 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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0469r:</customfieldvalue>

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