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
..
infra_drivers	Fix: VNF update_wait always raise exception	2019-09-09 04:44:42 +00:00
mgmt_drivers	Fix: VNF update_wait always raise exception	2019-09-09 04:44:42 +00:00
monitor_drivers	from i18n import _ when quoting them	2019-08-09 09:59:48 +08:00
policy_actions	Remove H903 error in source.	2019-02-22 11:10:20 +00:00
__init__.py	Device refactor Part3: Rename device in codes	2016-08-26 16:26:57 +08:00
keystone.py	Move to use only kestone v3 api	2019-03-06 05:09:13 +00:00
monitor.py	from i18n import _ when quoting them	2019-08-09 09:59:48 +08:00
plugin.py	Delete VNF should fail with 409 error	2020-01-31 13:54:49 +05:30
utils.py	Add new policy action: vdu_autoheal	2019-01-24 09:55:30 +09:00
vim_client.py	Fix bug that causes InternalServerError in FT	2020-01-16 14:16:55 +09:00