Cannot delete an IN_PROGRESS stack

[Steve Baker]

Since multi-engine was merged it is no longer possible to delete a stack which is create/update IN_PROGRESS:

$ heat delete config1
ERROR: Stack config1 already has an action (CREATE) in progress.

This is a regression, any in-progress create or update needs to be halted so that the lock can be taken for a delete. This would result in having to wait for the stack timeout for deleting some stacks which are known to be bad.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/63002

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/67971

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/67971
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=07884448fed64badcf8922c01c1ea044462584b7
Submitter: Jenkins
Branch: master

commit 07884448fed64badcf8922c01c1ea044462584b7
Author: Jason Dunsmore <email address hidden>
Date: Mon Jan 20 15:02:34 2014 -0600

    Add a new ThreadGroupManager class

    Introduce a ThreadGroupManager class to manage active ThreadGroups for
    engine services and move the thread-related EngineService methods to
    ThreadGroupManager. This will make it easier for multiple engine
    services to manage thread groups.

    Partial-Bug: #1262012
    Change-Id: I1ce7785021726c274a294ef402b036540d395a29

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/63002
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=42f788b56f02454cfa43e7801b62edeb50359c00
Submitter: Jenkins
Branch: master

commit 42f788b56f02454cfa43e7801b62edeb50359c00
Author: Jason Dunsmore <email address hidden>
Date: Mon Dec 16 14:16:26 2013 -0600

    Allow an in-progress stack to be deleted

    Since multi-engine was merged, it is no longer possible to delete a
    stack which is create/update IN_PROGRESS. This re-introduces that
    ability.

    If the current engine has an active stack lock, stop any active
    threads, remove the lock, and delete the stack. If another engine has
    the active stack lock, send an RPC command to the remote engine to stop
    any active threads and remove the lock, and then delete the stack
    locally. If no engines have the an active stack lock, acquire the lock
    and delete the stack.

    Closes-Bug: #1262012
    Change-Id: I188e43ad88b98da7d1a08269189aaefa57c36df2