https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/TRNSPRTPCE-444 transportpce <p>Few vendor devices doesn't support put operation which translates into a netconf replace operation. Current code in transportpce is using put operation for all device transaction. This is causing failure in service-creation process. As per rfc6241, default netconf operation is merge and it supported by all vendor implementation. </p> TRNSPRTPCE-444

All devices doesnt support put operation

Bug Medium Verified Done Shweta Vachhani Shweta Vachhani Wed, 21 Apr 2021 16:35:45 +0000 Fri, 3 Sep 2021 13:30:22 +0000 Thu, 22 Apr 2021 14:25:30 +0000 Silicon 0 2 <p>to <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=gthouenon" class="user-hover" rel="gthouenon">gthouenon</a> <a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=svachhani" class="user-hover" rel="svachhani">svachhani</a> </p> <p>If I understand well and if I don't mistake myself, the "put" operation is defined in RESTCONF (and HTTP) but not at all in NetCONF.<br/> But the statement deviceTx.put(LogicalDatastoreType.CONFIGURATION, rdmConnectionIID, rdmConnBldr.build()) is directly translated in a NETCONF rpc edit-config with a default operation "put" instead of "merge" or "none"</p> <p>I wonder whether we don't have a translation issue, perhaps with our upstream dependencies, here...</p> <p>Most vendors supports it but "put" is translated into "replace", which is not an exact equivalent.</p> Development Rank 0|i03xs7: