<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:15:48 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-754] Missing notification model -&gt; unknown RPC on simulated device</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-754</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;As said in change&#160;&lt;a href=&quot;https://git.opendaylight.org/gerrit/c/netconf/+/88643&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;GERRIT-CHANGE&lt;/a&gt;, we should advertise only the notification capability&#160;&quot;urn:ietf:params:netconf:capability:notification:1.0&quot; and we do not need to provide the model. We do exactly this&#160;in our netconf simulator(which is built on&#160; ODL simulator), but as it turns out it&apos;s still not enough and the built schema of netconf device after connection to controller is established (status connected) doesn&apos;t contain the &quot;urn:ietf:params:xml:ns:netconf:notification:1.0?revision=2008-07-14)create-subscription&quot; rpc.&lt;/p&gt;

&lt;p&gt;We tried to debug the whole process of building schema of connected netconf device and we found out that maybe the problem lies in &lt;a href=&quot;https://github.com/opendaylight/netconf/blob/release/aluminium-sr1/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/NetconfDevice.java#L185&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;getDeviceSpecificRpc&lt;/a&gt;&#160;where the handleSalInitializationSuccess is called with DOMRpcService with NetconfMessageTransformer built in &lt;a href=&quot;https://github.com/opendaylight/netconf/blob/release/aluminium-sr1/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/NetconfDevice.java#L378&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;getDeviceSpecificRpc-NetconfMessageTransformer&lt;/a&gt; which doesn&apos;t check if the device isNotificationSupported() and just calls the baseSchemas.getBaseSchema() which doesn&apos;t contain notification support.&lt;/p&gt;

&lt;p&gt;So the solution may be simple: change baseSchemas.getBaseSchema() to this.resolveBaseSchema() (which checks if the device should support notifications i.e it advertised the capability) in  &lt;a href=&quot;https://github.com/opendaylight/netconf/blob/release/aluminium-sr1/netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/NetconfDevice.java#L378&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;getDeviceSpecificRpc-NetconfMessageTransformer&lt;/a&gt;.&lt;br/&gt;
Is this something intentional and the simulated device should still provide the model as well?&lt;/p&gt;</description>
                <environment></environment>
        <key id="33768">NETCONF-754</key>
            <summary>Missing notification model -&gt; unknown RPC on simulated device</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="10001" iconUrl="https://jira.opendaylight.org/" description="">In Review</status>
                    <statusCategory id="4" key="indeterminate" colorName="yellow"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="IaroslavK">Iaroslav Kholiavko</assignee>
                                    <reporter username="marekzatko">Marek Za&#357;ko</reporter>
                        <labels>
                    </labels>
                <created>Fri, 29 Jan 2021 10:47:51 +0000</created>
                <updated>Mon, 22 Feb 2021 16:38:49 +0000</updated>
                                                            <fixVersion>Aluminium SR1</fixVersion>
                    <fixVersion>Aluminium SR2</fixVersion>
                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                    <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="21351">NETCONF-338</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|i03wxj:</customfieldvalue>

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