Operating System: Linux
Platform: PC

This is working in stable/helium with inventory URIs

Karaf log is available in the jenkins link.

The problem is: unknown child node in the payload:

Unknown child(ren) node(s) detected, identified by: (http://netconfcentral.org/ns/toaster)toaster

This is correct behavior in ODL since netopeer did not provide yang schema for the toaster module:

2015-05-17 00:39:46,758 | WARN | oupCloseable-6-2 | NetconfDeviceCommunicator | 171 - org.opendaylight.controller.sal-netconf-connector - 1.2.0.SNAPSHOT | RemoteDevice

: Error reply from remote device, request: <rpc message-id="m-3" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-schema xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
<identifier>toaster</identifier>
<version>2009-11-20</version>
<format xmlns:x="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">x:yang</format>
</get-schema>
</rpc>
, response: <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-3">
<rpc-error>
<error-type>protocol</error-type>
<error-tag>invalid-value</error-tag>
<error-severity>error</error-severity>
<error-message>The requested schema does not exist.</error-message>
</rpc-error>
</rpc-reply>

... there are more schemas that could not be downloaded, not only toaster.

You should configure netopeer to provide all necessary yang models.

This works with helium, because helium did not contain proper data validation and used CompositeNodes. Currently, NormalizedNodes are in use and they do not allow unknown children(according to the schema) in the payload. This was essentially a bug with the old mount point APIs and the test relied on it.

Hi Maros,

I can comment out the TC on Lithium but can you please update the netconf wiki with the things that currently work:

https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Examples:Netconf

Thanks/Luis

Yeah, the netopeer related stuff should probably be updated so that the installed netopeer works fine with ODL ..

Quick update:

Its not missing schemas in netopper after all. Its a bug in netopeer's libnetconf lib. The library cannot parse prefixed values in xml properly e.g. yang leaves with identityref type.

Get-schema rpc contains an identityref leaf for input parameter format. ODL serializes identityrefs properly, but netopper cannot parse them and returns rpc-error for each attempt to download yang schemas.

This xml is ok with netopper:
<rpc message-id="m-2" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-schema xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
<identifier>ietf-netconf</identifier>
<version>2011-03-08</version>
<format>yang</format>
</get-schema>
</rpc>

but this one is not:
<rpc message-id="m-2" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-schema xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
<identifier>ietf-netconf</identifier>
<version>2011-03-08</version>
<format xmlns:x="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">x:yang</format>
</get-schema>
</rpc>

Both above xmls are correct, but netopper accepts only the simpler one.

What we can do: optimize identityref serialization so that the prefix is not included if not necessary (like in above case where the namespace of serialized identity is equal to namespace of parent tag). This will optimize serialized xml and also serve as a workaround for when connecting to Netopper netconf.

In addition, we need to report that bug for libnetconf library.

https://git.opendaylight.org/gerrit/#/c/21610/

Maros could you provide link to libnetconfd bug?

https://code.google.com/p/libnetconf/issues/detail?id=63