Hi all, so with loading in the ietf-netconf-monitoring and ietf-netconf manually in cache/schema I'm able to connect to my netconf device.

It is able to retrieve the hello message and read it, however in the next step where it performs a ietf-netconf <get> request for the list schema in ietf-netconf-monitoring, I have yang files that augment that list with extra leaf nodes. OpenDaylight is attempting to parse this rpc xml reply however its giving me a warning as ODL doesn't know what to do with these reported nodes and says it's unable to detect available schemas though they are all reported.

Manual requests allows me to retrieve these schemas as well as the list. Is there a work around so ODL may initially ignore these reported augmented nodes to download the yang schemas? If it helps, my device uses the yumaworks-system yang file to augment this list with the two nodes: module-type and conformance. It's also reported that it is unable to set namespace context initially.

Thanks! If any more context is needed please let me know.

Looking further into the source code, I found in XmlParserStream.java in yangtools to throw the exception that is causing my issue on line 566. There is a comment at the conditional statement noting that the node is unhandled and it is still undecided what to do with the node. I see online that people have made test cases setting this boolean value "strictParsing" to false, which would solve my issue, however I have not seen a method from the current distribution that would allow me to set this setting to false when mounting a new NetConf device to the ODL controller so it can still automatically create the schema context. Is there a way to do this? Would one have to go through the process of adding to an existing feature in the open source project to achieve this goal?

Hello Roland,

On 19/01/2022 22:05, Ronald Hoang wrote:

Looking further into the source code, I found in XmlParserStream.java in yangtools to throw the exception that is causing my issue on line 566. There is a comment at the conditional statement noting that the node is unhandled and it is still undecided what to do with the node. I see online that people have made test cases setting this boolean value "strictParsing" to false, which would solve my issue, however I have not seen a method from the current distribution that would allow me to set this setting to false when mounting a new NetConf device to the ODL controller so it can still automatically create the schema context. Is there a way to do this? Would one have to go through the process of adding to an existing feature in the open source project to achieve this goal?

This (with the previous email) sounds like a problem with schema information/interpretation of a particular details.

Can you provide further details around the device and/or the steps to reproduce? Otherwise we are talking about (very difficult to bracket) theoretical scenarios, which are rather difficult to diagnose through emails...

Regards,
Robert