OpenDaylight JIRA

OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us

8.20.10

820010

22-06-2022

[NETCONF-228] executing rpc get-config in netconf protocol by post errors https://jira.opendaylight.org/browse/NETCONF-228 netconf <p>when executing rpc get-config in netconf protocol, errors happen if ietf-netconf.yang has different revision between odl and device(e.g netopeer)</p> <p>mehtod:<br/> post</p> <p> url: <br/> <a href="http://localhost:8181/restconf/operations/...../ietf-netconf:get-config(get" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/restconf/operations/...../ietf-netconf:get-config(get</a>)</p> <p>Operating System: Linux<br/> Platform: PC</p> NETCONF-228

executing rpc get-config in netconf protocol by post errors

Bug Resolved Cannot Reproduce Jakub Toth moon.lee Tue, 19 Jul 2016 04:33:09 +0000 Fri, 15 Mar 2019 22:22:26 +0000 Tue, 9 Aug 2016 07:17:57 +0000 restconf-nb 0 4 <p>Can you please provide a karaf.log?</p> <p>Can you also please provide what error exactly did you get?</p> <p>Do you really need to call get-config operation explicitly through restconf?<br/> Isn't accessing configuration data through restconf/config sufficient?</p> <p>(In reply to Jakub Morvay from comment #3)<br/> > Can you also please provide what error exactly did you get?<br/> > <br/> > Do you really need to call get-config operation explicitly through restconf?<br/> > Isn't accessing configuration data through restconf/config sufficient?</p> <p><p>Problem accessing /restconf/operations/network-topology:network-topology/topology/topology-netconf/node/turing/yang-ext:mount/ietf-netconf:get-config. Reason:<br/> <pre> Server Error</pre></p><h3>Caused by:</h3><pre>java.lang.IllegalArgumentException: Schema node null does not allow children.<br/> at org.opendaylight.yangtools.yang.data.impl.codec.SchemaTracker.<init>(SchemaTracker.java:86)<br/> at org.opendaylight.yangtools.yang.data.impl.codec.SchemaTracker.create(SchemaTracker.java:125)<br/> at org.opendaylight.yangtools.yang.data.codec.gson.JSONNormalizedNodeStreamWriter.<init>(JSONNormalizedNodeStreamWriter.java:48)<br/> at org.opendaylight.yangtools.yang.data.codec.gson.JSONNormalizedNodeStreamWriter.createNestedWriter(JSONNormalizedNodeStreamWriter.java:184)<br/> at org.opendaylight.controller.sal.rest.impl.NormalizedNodeJsonBodyWriter.createNormalizedNodeWriter(NormalizedNodeJsonBodyWriter.java:139)<br/> at org.opendaylight.controller.sal.rest.impl.NormalizedNodeJsonBodyWriter.writeNormalizedNode(NormalizedNodeJsonBodyWriter.java:100)<br/> at org.opendaylight.controller.sal.rest.impl.NormalizedNodeJsonBodyWriter.writeTo(NormalizedNodeJsonBodyWriter.java:78)<br/> at org.opendaylight.controller.sal.rest.impl.NormalizedNodeJsonBodyWriter.writeTo(NormalizedNodeJsonBodyWriter.java:46)</p> <p>(In reply to Jakub Morvay from comment #3)<br/> > Can you also please provide what error exactly did you get?<br/> > <br/> > Do you really need to call get-config operation explicitly through restconf?<br/> > Isn't accessing configuration data through restconf/config sufficient?</p> <p>yes, i need to call get-config operation through restconf to get multiple nodes informaton.</p> <p>(In reply to moon.lee from comment #5)<br/> > (In reply to Jakub Morvay from comment #3)<br/> > > Can you also please provide what error exactly did you get?<br/> > > <br/> > > Do you really need to call get-config operation explicitly through restconf?<br/> > > Isn't accessing configuration data through restconf/config sufficient?<br/> > <br/> > yes, i need to call get-config operation through restconf to get multiple<br/> > nodes informaton.</p> <p>Can please explain this multiple nodes information further?</p> <p>I think POST to<br/> /restconf/operations/network-topology:network-topology/topology/topology-netconf/node/turing/yang-ext:mount/ietf-netconf:get-config<br/> should be conceptually the same thing as GET to <br/> /restconf/config/network-topology:network-topology/topology/topology-netconf/node/turing/yang-ext:mount/</p> <p>What revision of ietf-netconf module are you using? Why do you think this is caused by revision mismatch?</p> <p>(In reply to Jakub Morvay from comment #6)<br/> > (In reply to moon.lee from comment #5)<br/> > > (In reply to Jakub Morvay from comment #3)<br/> > > > Can you also please provide what error exactly did you get?<br/> > > > <br/> > > > Do you really need to call get-config operation explicitly through restconf?<br/> > > > Isn't accessing configuration data through restconf/config sufficient?<br/> > > <br/> > > yes, i need to call get-config operation through restconf to get multiple<br/> > > nodes informaton.<br/> > <br/> > Can please explain this multiple nodes information further?<br/> > <br/> > I think POST to<br/> > /restconf/operations/network-topology:network-topology/topology/topology-<br/> > netconf/node/turing/yang-ext:mount/ietf-netconf:get-config<br/> > should be conceptually the same thing as GET to <br/> > /restconf/config/network-topology:network-topology/topology/topology-netconf/<br/> > node/turing/yang-ext:mount/<br/> > <br/> > What revision of ietf-netconf module are you using? Why do you think this is<br/> > caused by revision mismatch?</p> <p>these two operations are not same. see <a href="https://jira.opendaylight.org/browse/NETCONF-230" title="operations "get" and "get-config" are not distinguished from get http://restconf/config/... or post http://restconf/operations/..." class="issue-link" data-issue-key="NETCONF-230"><del>NETCONF-230</del></a>.</p> <p>revision of ietf-netconf in odl is 2011-06-11, in netopeer I use is 2011-03-08</p> <p>Does netopeer advertise ietf-netconf capability with revision 2011-03-08 in hello message?</p> <p>(In reply to Jakub Morvay from comment #8)<br/> > Does netopeer advertise ietf-netconf capability with revision 2011-03-08 in<br/> > hello message?</p> <p>Yes,it advertises.</p> <p>(In reply to moon.lee from comment #9)<br/> > (In reply to Jakub Morvay from comment #8)<br/> > > Does netopeer advertise ietf-netconf capability with revision 2011-03-08 in<br/> > > hello message?<br/> > <br/> > Yes,it advertises.</p> <p>In that case, you should be able to call even base netconf operations through restconf, so it looks something is broken. </p> <p>Can you please provide us karaf.log, so we can have more information, what is really happening.</p> <p>Attachment karaf.log has been added with description: karaf.log</p> <p>Hi </p> <p>by looking at package names in log e.g:</p> <p>org.opendaylight.controller.sal.rest.impl.NormalizedNodeJsonBodyWriter<br/> you are using pre-Beryllium Restconf which is not supported anymore. <br/> Can you please switch to stable Beryllium first and try again? Many thanks.</p> <p> Best Regards</p> <p> Martin</p> <p>Is this supported in Boron? My apologies, I was on PTO for the call today and may have missed out on the conversation, still reviewing the minutes. It seems like something we ought to support going forward... I don't think that it is particular to pre-Beryllium as I believe this wont work in post-beryllium either...</p> <p>Right. </p> <p>We've managed to replicate this bug with latest code base and it seems to be a real issue. Given rpc get-config is not present in rpcs collection, even though ietf-netconf module is part of schema context. <br/> We're currently investigating why this is happening and we'll keep you updated.<br/> Bug reopen, set to critical back again.</p> <p> Martin</p> <p>Hi all,</p> <p>If the device advertises ietf-netconf capability, you are able to call base netconf rpcs via restconf. Tested on master branch, Beryllium should behave in the same way.</p> <p>Martin replicated this bug on ODL netconf northbound, not on mounted device.<br/> Since this bug is about calling base netconf rpcs on mounted device, I am closing this bug.</p> Duplicate NETCONF-229 NETCONF-230 Development External issue ID 6209 External issue URL Issue Type ODL SR Target Milestone Rank 0|i01x8v: