Description of problem: It's not clear exactly how we get in this state, but it's possible for the delete path to encounter resources with associated users, where those users don't exist (perhaps after re-trying a previously failed delete). How reproducible: If you do an out of band deletion of the user, always, otherwise it seems to happen inconsistently. Reported in openstack-heat-engine-5.0.0-1.el7ost.noarch Steps to Reproduce: See reproducer in linked upstream bug Actual results: The stack can be DELETE_FAILED, permanently. Expected results: A stack should never be persistently impossible to delete Additional info: Upstream bug, with fix merged - https://bugs.launchpad.net/heat/+bug/1505981
Ack'ed. Moving to OSP8 GA.
FWIW I had again the DELETE_FAILED issue and the gerrit patch fixed it for me
We can manage to squeeze it in z3. Moving the target.
Still not sure of the trigger, but bug 1285495 may be related.
AFAIT I was always able to delete a stack in failed state in the latest versions. I think that this issue can be ignored now because there was no way to reproduce it and I can't as well. If there is a more specific issue that we can track, please open a new bug.
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:2680