It is not possible to create or update the network-topology configuration data by Restconf JSON content-based PUT operation.

The Restconf JSON PUT operation returns ok, however when reading back the data it can be seen that nothing is being created inside the network-topology configuration data.

For example when issuing:

PUT http://127.0.0.1:8181/restconf/config/network-topology:network-topology

application/json

{
"network-topology": {
"topology": [

{ "topology-id": "test" }

]
}
}

However when reading back by Restconf GET, the following error is reported:

GET http://127.0.0.1:8181/restconf/config/network-topology:network-topology

application/json

ERROR OCCURRED:404
{
"errors":{
"error":[

{ "error-message":"Request could not be completed because the relevant data model content does not exist." , "error-tag":"data-missing", "error-type":"application" }

]
}
}

On the other hand, network-topology:network-topology configuration data can be read by Restconf GET and deleted by Restconf DELETE operations when already present as a result of the behavior of some feature installation (such as odl-netconf-connector-all, for example).

Workaround is to take advantage of application/xml content in place of JSON one.

As a attachment a file reporting the step I performed to reproduce systematically such issue.