tacker/api-ref/source/v1/samples/vnfs
Shubham Potale 938262073f Delete VNF should fail with 409 error
If user deletes VNF in "PENDING_CREATE" status, VNF is deleted from
tacker but the resources created by VIM driver are not cleaned up
properly. This patch doesn't allow VNF to be deleted if the status is
in "PENDING_CREATE" status. It will raise 409 error.

APIImpact
Return 409 error instead of 200 when VNF is deleted in
"PENDING_CREATE" status.

Change-Id: I2de9c3dce5a4b3795119e2550aa8acea68940c45
Closes-Bug: #1798726
2020-01-31 13:54:49 +05:30
..
vnfs-actions-create-request.json API reference documentation 2016-12-01 14:17:47 +09:00
vnfs-actions-create-response.json API reference documentation 2016-12-01 14:17:47 +09:00
vnfs-create-request.json API reference documentation 2016-12-01 14:17:47 +09:00
vnfs-create-response.json Parameter changed from mgmt_url to mgmt_ip_address 2019-01-31 10:08:17 +00:00
vnfs-delete-request.json Delete VNF should fail with 409 error 2020-01-31 13:54:49 +05:30
vnfs-inline-create-request.json Update cirros to 0.4.0 2018-07-25 01:42:48 +00:00
vnfs-list-response.json Parameter changed from mgmt_url to mgmt_ip_address 2019-01-31 10:08:17 +00:00
vnfs-resources-list-response.json API reference documentation 2016-12-01 14:17:47 +09:00
vnfs-show-response.json Parameter changed from mgmt_url to mgmt_ip_address 2019-01-31 10:08:17 +00:00
vnfs-update-request.json API reference documentation 2016-12-01 14:17:47 +09:00
vnfs-update-response.json Parameter changed from mgmt_url to mgmt_ip_address 2019-01-31 10:08:17 +00:00