Hi everyone,
We are having a problem with this exception when populating data plane locators
for service functions at SFC project.
Exception in thread "CommitFutures-0"
org.opendaylight.netconf.sal.restconf.impl.RestconfDocumentedException: errors:
[RestconfError [error-type: application, error-tag: operation-failed,
error-message: canCommit encountered an unexpected failure, error-info:
TransactionCommitFailedException{message=canCommit encountered an unexpected
failure, errorList=[RpcError [message=canCommit encountered an unexpected
failure, severity=ERROR, errorType=APPLICATION, tag=operation-failed,
applicationTag=null, info=null, cause=java.lang.IllegalArgumentException: Node
(urn:cisco:params:xml:ns:yang:sfc-sf?revision=2014-07-01)sf-data-plane-locator[{(urn:cisco:params:xml:ns:yang:sfc-sf?revision=2014-07-01)name=dpl-101}]
is missing mandatory descendant
/(urn:intel:params:xml:ns:yang:sfc-sf-proxy?revision=2016-01-25)proxy-data-plane-locator/locator-type]]}
at
org.opendaylight.controller.md.sal.dom.broker.impl.TransactionCommitFailedExceptionMapper.newWithCause(TransactionCommitFailedExceptionMapper.java:37)
[...]
It seems a bit confusing since the error shows a problem with sfc-sf-proxy but
we are not creating any sfc-sf-proxy data. As you can see, to reproduce the
problem we do:
feature:install odl-sfc-provider-rest
Next, populate this service-function:
/restconf/config/service-function:service-functions/service-function/dpi-102-100/
{
"service-function": [
{
"name": "dpi-102-100",
"type": "dpi",
"nsh-aware": true,
"sf-data-plane-locator": [
{
"name": "dpl-100",
"port": 10100,
"ip": "10.3.1.102",
"service-function-forwarder": "SFF-bootstrap",
"transport": "service-locator:vxlan-gpe"
}
],
"ip-mgmt-address": "10.3.1.102",
"rest-uri": "http://localhost:10100";
}
]
}
And then populating this data causes the mentioned exception:
/restconf/config/service-function:service-functions/service-function/dpi-102-100/sf-data-plane-locator/dpl-101
{
"sf-data-plane-locator": [
{
"name": "dpl-101",
"port": 10101,
"ip": "10.3.1.105",
"service-function-forwarder": "SFF-bootstrap",
"transport": "service-locator:vxlan-gpe"
}
]
}
Is anyone familiar with this issue? Is there really a problem with a mandatory
missing descendant or is the exception's slogan misleading?
Thank you,
Best Regards,
Miguel Ángel.
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
