Heat stack-delete fails with HTTP/1.1 204 No Content.

Issue

• stack-delete command to delete specific stacks have been stuck.

# heat --os-tenant-name <TENANT_NAME1> stack-list
+--------------------------------------+-----------------------+--------------------+----------------------+
| id                                   | stack_name            | stack_status       | creation_time        |
+--------------------------------------+-----------------------+--------------------+----------------------+
| 638e84e0-13de-5781-ce41-a4f9d8f1c520 | <NO_EXISTENT_STACK-1> | DELETE_IN_PROGRESS | 2016-01-21T17:18:27Z |
| 3f6246ce-66e6-52c6-9b1e-4dd35e29c0d5 | <NO_EXISTENT_STACK-2> | DELETE_IN_PROGRESS | 2016-01-21T17:21:41Z |
| c13029f6-411e-51ec-9d13-53510fa753b9 | <STACK_NAME-3>        | CREATE_COMPLETE    | 2016-02-01T17:45:23Z |
+--------------------------------------+-----------------------+--------------------+----------------------+

• when running heat stack-delete with debug option again, we can see the following output - HTTP/1.1 204 No Content.

# heat --os-tenant-name <TENANT_NAME1> --debug stack-delete <NO_EXISTENT_STACK-1>
  <...>
  DEBUG (connectionpool:383) "DELETE /v1/1aa37eb368f050da956f0f81d99003c6/stacks/ <NO_EXISTENT_STACK-1>/638e84e0-13de-5781-ce41-a4f9d8f1c520 HTTP/1.1" 204 0

  HTTP/1.1 204 No Content

# heat --os-tenant-name <TENANT_NAME1> --debug stack-delete <NO_EXISTENT_STACK-2>
  <...>
  DEBUG (connectionpool:383) "DELETE /v1/1aa37eb368f050da956f0f81d99003c6/stacks/<NO_EXISTENT_STACK-2>/3f6246ce-66e6-52c6-9b1e-4dd35e29c0d5 HTTP/1.1" 204 0

  HTTP/1.1 204 No Content

As we can see , it looks those stacks have gone already ,but it looks they are still sitting in heat database.