Hi ,

I am facing strange issue. For one of our device running with recent
revision of yang model,  when performing restconf invocation for the
functionality available in older release too, the order of  argument
received as seen the karof log , constructed uri ,  is not in accordance
with the yang schema model hence edit-config call have this argument in the
order which is not according to the yang schema loaded on the device. Hence
device is rejecting this configuration.

However if we try with older software on the device , same functionality
works as controller receives the argument in the expected order .

This anomaly happens only for the delete configuration ...

What could be reason for this failure ?? Any help on this would be really

controller-dev mailing list

Reply via email to