Description of problem: On OSP 4 when attempting to delete heat stack -stuck at DELETE_IN_PROGRESS On previous scenarios have deleted the stack by "updating" just updated the resource_status field for marking DELETE_COMPLETE , heat stack delete was DELETE_IN_PROGRESS and then moving to DELETE_FAILED. Then "heat stack-delete" was completed but that left you with several "orphan" resources that need to be deleted in order to clean up the tenant. Currently as some roll-back was performed returning from a previous Icehouse upgrade the current situation appears again. Version-Release number of selected component (if applicable): openstack-heat-api-2014.1.4-1.el6ost.noarch openstack-heat-api-cfn-2014.1.4-1.el6ost.noarch openstack-heat-api-cloudwatch-2014.1.4-1.el6ost.noarch openstack-heat-common-2014.1.4-1.el6ost.noarch openstack-heat-engine-2014.1.4-1.el6ost.noarch openstack-heat-templates-0-0.3.20140407git.el6ost.noarch
Probably the least-invasive thing to do in the DB would be to move anything with an IN_PROGRESS status (both stack and resources) to the corresponding FAILED status. (Later versions of Heat handle this better automatically, but not Icehouse.) After that you can try deleting the stack again through the API - if resources are in the DELETE_FAILED status then Heat will attempt to clean them up again on the next delete, so you won't get orphans left behind like you would if you set them to DELETE_COMPLETE directly in the DB.
based on last comment the issue reported here has been resolved. the remaining inconsistency issues related to the rollback will be addressed separately.