Bug 1286118

Summary:	Deleting stack can fail persistently due to missing user
Product:	Red Hat OpenStack	Reporter:	Steven Hardy <shardy>
Component:	openstack-heat	Assignee:	Zane Bitter <zbitter>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	7.0 (Kilo)	CC:	jcoufal, mburns, michele, rbiba, rhel-osp-director-maint, sbaker, shardy, yeylon
Target Milestone:	z3	Keywords:	ZStream
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-heat-2015.1.2-3.el7ost	Doc Type:	Bug Fix
Doc Text:	Heat did not ignore a "Not Found" exception when trying to fetch a stack user; that is, a Keystone user created to allow servers deployed in the stack to authenticate back to Heat. As a consequence, if the stack user was deleted for any reason, Heat was unable to delete the associated stack. With this update, Heat catches the "Not Found" exception in this case. As a result, stacks can still be deleted even if their associated stack user is already missing.	Story Points:	---
Clone Of:
Clones:	1299477 (view as bug list)		Environment:
Last Closed:	2015-12-21 17:03:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Steven Hardy 2015-11-27 11:22:11 UTC

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

Comment 2 Jaromir Coufal 2015-12-01 11:12:53 UTC

Ack'ed. Moving to OSP8 GA.

Comment 4 Michele Baldessari 2015-12-02 20:19:11 UTC

FWIW I had again the DELETE_FAILED issue and the gerrit patch fixed it for me

Comment 5 Jaromir Coufal 2015-12-03 13:55:25 UTC

We can manage to squeeze it in z3. Moving the target.

Comment 8 Zane Bitter 2015-12-03 21:33:18 UTC

Still not sure of the trigger, but bug 1285495 may be related.

Comment 9 Amit Ugol 2015-12-09 13:53:30 UTC

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.

Comment 11 errata-xmlrpc 2015-12-21 17:03:36 UTC

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