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
(cherry picked from commit 0d2031a5c408ef5919387c680eeaac68709a0f6c)
Reviewed: https:/ /review. openstack. org/543345 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=29b3eada891 d9599eb3c284af2 174868cb11a4fd
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 29b3eada891d959 9eb3c284af21748 68cb11a4fd
Author: Rajesh Tailor <email address hidden>
Date: Wed Jan 3 13:31:38 2018 +0530
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: Ida1a9d8761cec9 585f031ec25e569 2b8bb55661e 919387c680eeaac 68709a0f6c)
Closes-Bug: #1741000
(cherry picked from commit 0d2031a5c408ef5