Ignore ModifiedNodeDoesNotExistException on delete 03/19803/1
authorDan Timoney <dtimoney@att.com>
Thu, 19 Oct 2017 20:03:04 +0000 (16:03 -0400)
committerDan Timoney <dtimoney@att.com>
Thu, 19 Oct 2017 20:03:56 +0000 (16:03 -0400)
commit45ac56ef4f49b57bee4aa2cd52e4e41618ae2251
tree87f69e5e3b030058047f531ef4ac7e03fea1a5c6
parent5fa42107512d9b06cb73877dd35739a0b5186840
Ignore ModifiedNodeDoesNotExistException on delete

When trying to deleteVnf from operational or config tree, if a
ModifiedNodeDoesNotExistException is cause for commit exception
it means that the data you are trying to delete does not exist.
So you wanted it gone, it's already gone ... log a message at
debug level but don't fail the transaction.

Change-Id: Iea0f4e78522cc2f437843e2b17080855cd314ea6
Issue-ID: SDNC-137
Signed-off-by: Dan Timoney <dtimoney@att.com>
generic-resource-api/model/src/main/yang/GENERIC-RESOURCE-API.yang
vnfapi/provider/src/main/java/org/onap/sdnc/vnfapi/vnfapiProvider.java