[TRNSPRTPCE-444] All devices doesnt support put operation Created: 21/Apr/21  Updated: 03/Sep/21  Resolved: 22/Apr/21

Status: Verified
Project: transportpce
Component/s: None
Affects Version/s: None
Fix Version/s: Silicon

Type: Bug Priority: Medium
Reporter: Shweta Vachhani Assignee: Shweta Vachhani
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

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. 

 Comments   
Comment by Guillaume Lambert [ 22/Apr/21 ]

to gthouenon svachhani

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.
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"

I wonder whether we don't have a translation issue, perhaps with our upstream dependencies, here...

Comment by Guillaume Lambert [ 22/Apr/21 ]

Most vendors supports it but "put" is translated into "replace", which is not an exact equivalent.

Generated at Wed Feb 07 20:43:06 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.