<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:04:35 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>[INTTEST-107] add CSIT test cases to cover rpc action</title>
                <link>https://jira.opendaylight.org/browse/INTTEST-107</link>
                <project id="10189" key="INTTEST">integration-test</project>
                    <description>&lt;p&gt;While debugging &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-702&quot; title=&quot;Regression in NETCONF ACTION Test&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-702&quot;&gt;&lt;del&gt;NETCONF-702&lt;/del&gt;&lt;/a&gt;, I realized there is no unit test coverage for these cases.&lt;br/&gt;
The fix for &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-696&quot; title=&quot;Invoking Yang 1.1 Action on ODL fails for Yang Model containing yang action under augmentation hierarchy.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-696&quot;&gt;&lt;del&gt;NETCONF-696&lt;/del&gt;&lt;/a&gt; created a regression caught in CSIT, which is how we ended&lt;br/&gt;
up with &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-702&quot; title=&quot;Regression in NETCONF ACTION Test&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-702&quot;&gt;&lt;del&gt;NETCONF-702&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;We need four test cases to pass. two already exist, but one is now failing (the regression)&lt;br/&gt;
&lt;a href=&quot;https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netconf-csit-1node-userfeatures-all-magnesium/288/robot-plugin/log.html.gz#s1-s5-s1-t6&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;passing case&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netconf-csit-1node-userfeatures-all-magnesium/288/robot-plugin/log.html.gz#s1-s5-s1-t7&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;newly failing case (but used to pass) &lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Essentially, it&apos;s doing the same thing, which is hitting this URI twice:&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;
/rests/data/network-topology:network-topology/topology=topology-netconf/node={{node}}/yang-ext:mount/example-action:interfaces/&lt;span class=&quot;code-keyword&quot;&gt;interface&lt;/span&gt;=eth1/reset
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The first (passing case) is using an XML request and body:&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;
&amp;lt;?xml version=&lt;span class=&quot;code-quote&quot;&gt;&quot;1.0&quot;&lt;/span&gt; encoding=&lt;span class=&quot;code-quote&quot;&gt;&quot;UTF-8&quot;&lt;/span&gt;?&amp;gt;
&amp;lt;input xmlns=&lt;span class=&quot;code-quote&quot;&gt;&quot;https:&lt;span class=&quot;code-comment&quot;&gt;//example.com/ns/example-action&quot;&lt;/span&gt;&amp;gt;
&lt;/span&gt;    &amp;lt;delay&amp;gt;600&amp;lt;/delay&amp;gt;
&amp;lt;/input&amp;gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;and the failing case is JSON:&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;
{
    &lt;span class=&quot;code-quote&quot;&gt;&quot;example-action:input&quot;&lt;/span&gt;: {
        &lt;span class=&quot;code-quote&quot;&gt;&quot;delay&quot;&lt;/span&gt;: 600
    }
}
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The URI it&apos;s triggering is triggering an RPC action which is defined in one of the&lt;br/&gt;
schemas that is used to mount the netconf testtool. The schemas are in the&lt;br/&gt;
int/test repo, &lt;a href=&quot;https://github.com/opendaylight/integration-test/tree/master/csit/variables/netconf/CRUD/schemas&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;here&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The original bug that produced the fix that created this regression was related to&lt;br/&gt;
calling an RPC on an action from a yang augmentation which is defined a little&lt;br/&gt;
differently in the yang files. To recreate this scenario, there are two yang files&lt;br/&gt;
attached to &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-696&quot; title=&quot;Invoking Yang 1.1 Action on ODL fails for Yang Model containing yang action under augmentation hierarchy.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-696&quot;&gt;&lt;del&gt;NETCONF-696&lt;/del&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://jira.opendaylight.org/secure/attachment/15655/augment-main-a%402014-01-21.yang&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;augment-main-a@2014-01-21.yang &lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://jira.opendaylight.org/secure/attachment/15656/main@2014-01-21.yang&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;main@2014-01-21.yang &lt;/a&gt;&lt;/p&gt;

&lt;p&gt;if those files are added to the int/test repo schemas/ folder then the same suite with&lt;br/&gt;
the already existing test cases will have the ability for the next two test cases needed.&lt;br/&gt;
They are identical to the already existing cases, but they will use a different URI that&lt;br/&gt;
points to the new RPC action from the augmention. This one:&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;
rests/data/network-topology:network-topology/topology=topology-netconf/node={{node}}/yang-ext:mount/main:cont/cont1/reset
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</description>
                <environment></environment>
        <key id="32794">INTTEST-107</key>
            <summary>add CSIT test cases to cover rpc action</summary>
                <type id="10102" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10316&amp;avatarType=issuetype">Sub-task</type>
                            <parent id="32568">INTTEST-81</parent>
                                    <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="3" iconUrl="https://jira.opendaylight.org/images/icons/statuses/inprogress.png" description="This issue is being actively worked on at the moment by the assignee.">In Progress</status>
                    <statusCategory id="4" key="indeterminate" colorName="yellow"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="kailashkhalasi">Kailash Khalasi</assignee>
                                    <reporter username="jluhrsen">Jamo Luhrsen</reporter>
                        <labels>
                            <label>CSIT</label>
                            <label>netconf</label>
                    </labels>
                <created>Wed, 24 Jun 2020 22:57:31 +0000</created>
                <updated>Mon, 29 Jun 2020 15:15:49 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                    <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="32704">NETCONF-696</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="32785">NETCONF-702</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|i03t93:</customfieldvalue>

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