Operating System: Linux
Platform: PC

Attachment first issue .txt has been added with description: Exception Stack Trace for both Issues

Could you please investigate how correct Netconf request for your device look like?

ODL sended get request like this:

<rpc message-id="m-6" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source>
<running/>
</source>
<filter>
<configuration xmlns="http://xml.juniper.net/xnm/1.1/xnm"/>
</filter>
</get-config>
</rpc>

Where filter <configuration xmlns="http://xml.juniper.net/xnm/1.1/xnm"/>
is constructed from your YANG model and restconf URL:
/configuration:configuration

This means your model configuration has top level container configuration.

Netconf device reported back

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns:junos="http://xml.juniper.net/junos/14.2I0/junos" message-id="m-6">
<rpc-error>
<error-type>protocol</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-message>syntax error, expecting <config-text/> or <configuration></error-message>
<error-info>
<bad-element>configuration</bad-element>
</error-info>
</rpc-error>
</rpc-reply>

So it seems
a) configuration element should contain additional information
b) configuration element is in wrong namespace.

Since I do not know implementation of Netconf device neither YANG model,
this are assumptions.

COuld you try to do only GET http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/node/m10schemanew/yang-ext:mount/

Correct netconf request for my device is as follows,

<rpc message-id="m-0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source>
<running/>
</source>
<filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
<configuration xmlns="http://yang.juniper.net/yang/1.1/jc">
<system/>
</configuration>
</filter>
</get-config>
</rpc>

Yes my device has top level container configuration and I have added yang schema source in cache/schema folder and in connector xml as yang-module-capability.

I already did try this operational url and logs for the same are there in attached file with first point Exception Stack trace for first issue

GET http://localhost:8080/restconf/operational/opendaylight-inventory:nodes/node/m10schemanew/yang-ext:mount/

Same device is working fine with older version of ODL but latest one has issues

Correction in above information is as follows

Correct netconf request for my device is as follows,

<rpc message-id="m-0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source>
<running/>
</source>
<filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
<configuration xmlns="http://xml.juniper.net/xnm/1.1/xnm">
<system/>
</configuration>
</filter>
</get-config>
</rpc>

Does request

<rpc message-id="m-0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source>
<running/>
</source>
<filter xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:type="subtree">
<configuration xmlns:junos="http://xml.juniper.net/xnm/1.1/xnm">
</configuration>
</filter>
</get-config>
</rpc>

Works for you?

Because examples you showed are one level nested (equivalent of http://localhost:8080/restconf/config/opendaylight-inventory:nodes/node/m10schemanew/yang-ext:mount/configuration:configuration/system ).

Hi Tony,

Thanks for time.
You guessed it right there was issue in device OS so, so got it corrected and its working now we can close this bug now.