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: | ||||
: | 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
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 |