Rollback fails with changes in the Aether ROC API: "key field has nil value <nil>"

[afuentesconwet]

I have tried applying rollbacks to configurations done both using the Aether ROC GUI and the Aether ROC API; ensuring that in both cases all the data necessary for the different assets was provided; as well as ensuring that I was pointing to the latest change applied in the network, and in all the cases, I have received responses of the like:

$ onos config rollback 22 Rollback failed: rpc error: code = Unknown desc = error in creating config struct from IETF JSON data: key field ip-domain-id (*string) has nil value <nil> rpc error: code = Unknown desc = error in creating config struct from IETF JSON data: key field ip-domain-id (*string) has nil value <nil>

The endpoint for the following request:
http://192.168.64.2:8181/aether/v2.0.x/connectivity-service-v2/enterprises/enterprise/aiab-enterprise/site/aiab-site/ip-domain/ipdomain123

Here is an example of one of the changes using the ROC REST API:
{ "admin-status": "ENABLE", "description": "IP domain", "display-name": "ipdomain123", "dnn": "internet", "dns-primary": "127.0.0.1", "dns-secondary": "127.0.0.1", "ip-domain-id": "ipdomain123", "mtu": 0, "subnet": "10.66.66.66/32" }

The result of the operation is 201 Created, with a UUID of "uuid:685f0fb2-cf73-415b-974a-053f1909a509".

The same tests have been tried using the ROC GUI with the same result, and for different types of assets. We do not urgently need the GUI to work for these cases, so we can focus on the issue when making calls with the REST API.

[afuentesconwet]

Further testing the behavior, apparently the rollback is applied; the only thing is that the onos config command returns an RPC error.