Rajesh Tailor 0d2031a5c4 Allow force-delete even if task_state is not None ... As of now, if vm task_state is not 'None', and user tries to force-delete instance, then he gets HTTP 500 Error and instance deletion doesn't progress. The same is not the case, when user tries with delete api instead of force-delete api, even if vm task_state is not 'None'. Fixed the issue by allowing force-delete to delete instance in task_state other than None. Change-Id: Ida1a9d8761cec9585f031ec25e5692b8bb55661e Closes-Bug: #1741000		2018-01-31 15:30:40 +05:30
..
functional	Merge "[placement] Add sending global request ID in delete (3)"	2018-01-31 00:29:34 +00:00
live_migration/hooks	Fix live migration grenade ceph setup	2017-10-26 17:53:15 -04:00
unit	Allow force-delete even if task_state is not None	2018-01-31 15:30:40 +05:30
__init__.py	…
fixtures.py	[api] Allow multi-attach in compute api	2018-01-22 10:45:13 -05:00
json_ref.py	Nits from Ic3ab7d60e4ac12b767fe70bef97b327545a86e74	2017-11-28 15:55:45 +01:00
uuidsentinel.py	Remove redundant str typecasting	2016-09-23 12:53:34 +05:30