Bug 1242796
Summary: | Heat does not deletes failed stack at the first try | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Attila Fazekas <afazekas> |
Component: | openstack-heat | Assignee: | Steve Baker <sbaker> |
Status: | CLOSED DUPLICATE | QA Contact: | Amit Ugol <augol> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | Director | CC: | mburns, oblaut, rybrown, sbaker, shardy, yeylon, zbitter |
Target Milestone: | z2 | Keywords: | Triaged, ZStream |
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-09 22:07:09 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
Attila Fazekas
2015-07-14 08:21:05 UTC
It appears that you attempted to delete the stack before it had finished creating (or finished entering the CREATE_FAILED state). Since it had not completed its running action, the delete failed. When you tried again, the delete succeeded because the creation had finished failing. @Ryan: I think what actually can happen (I just hit a similar issue) is that if a stack ends up CREATE_FAILED because a nova server is in an ERROR state, we then try to delete it, but misinterpret the existing ERROR state as a failed delete. The server is still deleted, so you end up doing multiple deletes until all servers have actually been deleted. It's fixed upstream: https://bugs.launchpad.net/heat/+bug/1463716 *** Bug 1242983 has been marked as a duplicate of this bug. *** Actually I think the upstream fix is this one https://review.openstack.org/#/c/204301/ Without this fix, any stack-update or stack-delete on a CREATE_FAILED stack will likely fail @Ryan: I did not copy pasted all response in all cases, but the overcloud named stack was in *_FAILED, otherwise the delete would be rejected by the api. *** This bug has been marked as a duplicate of bug 1256564 *** |