Comment 4 for bug 1592374

Actually, it may be unrelated to convergence - I'm seeing this after switching convergence off:

| a2bd165e-4ee3-429b-8de5-c39fc4492773 | SoftwareDeploymentGroupTest-2043582773 | DELETE_IN_PROGRESS | 2016-06-14T13:40:51 | None | None |
| 2dcb5325-d280-43bd-be1a-39ed5ad5656a | SoftwareDeploymentGroupTest-2043582773-deployment-ev7qtvvfbh3t | CREATE_IN_PROGRESS | 2016-06-14T13:40:52 | None | a2bd165e-4ee3-429b-8de5-c39fc4492773 |
+--------------------------------------+----------------------------------------------------------------+--------------------+---------------------+---------------------+--------------------------------------+
-bash-4.3$ heat stack-delete 2dcb5325-d280-43bd-be1a-39ed5ad5656a
WARNING (shell) "heat stack-delete" is deprecated, please use "openstack stack delete" instead
Are you sure you want to delete this stack(s) [y/N]? y
ERROR: Stack SoftwareDeploymentGroupTest-2043582773-deployment-ev7qtvvfbh3t already has an action (CREATE) in progress.

I'm trying to manually delete the nested stack, and it's not working.

Only clue in the log is:
2016-06-14 14:46:02.123 DEBUG heat.engine.stack_lock [req-ced0d1a1-7914-4628-9058-b5aaaa5704f4 None admin] Lock on stack 2dcb5325-d280-43bd-be1a-39ed5ad5656a is owned by engine c118faa9-dec1-4a74-83a7-37261c96ad2f from (pid=32638) acquire /opt/stack/heat/heat/engine/stack_lock.py:69

So, maybe we're just not stealing the lock correctly in general. I know there are a couple of bugs open for this sort of issue for non-convergence when failures require cancelling in-progress operations on nested stacks, but I'm not clear atm if this is the same issue.