If use_heat = True after deleting trove instance heat still have stack, but it's empty without ability to be deleted (ghosted).
Steps to reproduce:
1. Create instance with heat as prov. service.
2. Delete instance.
3. Delete stack manualy.
Trove delete also should be
If a server is already deleted for some reason, the stack will fail to delete. It's better to handle this more gracefully instead of raising an exception.
# heat resource-show a b
+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
| description | |
| links | <SANITEZED>| | | <SANITEZED> |
| logical_resource_id | b |
| physical_resource_id | 03e23d82-a8bf-4df5-8d94-0b84ed229c83 |
| required_by | |
| resource_name | b |
| resource_status | DELETE_FAILED |
| resource_status_reason | NotFound: Instance could not be found (HTTP 404) (Request-ID: req-c6af6748-70ae-45ba-9105-acbc5e3e436c) |
| resource_type | OS::Nova::Server |
| updated_time | 2014-01-12T23:15:32Z |
+------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------+
It's better if this is handled more gracefully by simply handling the exception and assuming it's already deleted then.
Fix proposed to branch: master
Review: https:/