+++ This bug was initially created as a clone of Bug #1230163 +++ Description of problem: When I get CREATE_FAILED in deployments and try to delete the stack - it always ends up in DELETE_FAILED state and I have no work around. I need to reprovision the machine. This bug is to track heat fixes for deleting stacks which are already in a FAILED state.
*** Bug 1242796 has been marked as a duplicate of this bug. ***
*** Bug 1253493 has been marked as a duplicate of this bug. ***
Verified: openstack-heat-common-2015.1.1-5.el7ost.noarch openstack-heat-api-cfn-2015.1.1-5.el7ost.noarch openstack-heat-api-cloudwatch-2015.1.1-5.el7ost.noarch openstack-heat-api-2015.1.1-5.el7ost.noarch openstack-heat-templates-0-0.6.20150605git.el7ost.noarch openstack-heat-engine-2015.1.1-5.el7ost.noarch openstack-tripleo-heat-templates-0.8.6-69.el7ost.noarch Was able to delete the overcloud on a first attempt after a failed attempt to update it (which caused it to appear as failed).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2015:1865