Bug 1267364
Summary: | Stack updates from a dead heat-engine remain IN_PROGRESS | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Zane Bitter <zbitter> |
Component: | openstack-heat | Assignee: | Zane Bitter <zbitter> |
Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> |
Severity: | unspecified | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 (Kilo) | CC: | ddomingo, gbarros, jprovazn, mburns, rhel-osp-director-maint, sbaker, shardy, yeylon, zbitter |
Target Milestone: | async | Keywords: | Triaged, ZStream |
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-heat-2015.1.1-7.el7ost | Doc Type: | Bug Fix |
Doc Text: |
During startup, Heat incorrectly ignored nested stacks when searching for stacks with interrupted operations (for example, ones form a previous heat-engine process exiting). In addition, while those stacks that were not ignored were correctly set to FAILED, their resources remained IN_PROGRESS.
Because the resources remained IN_PROGRESS, it was not possible to recover the stacks when heat-engine was restarted.
With this update, nested stacks are now included when searching for interrupted operations, and IN_PROGRESS resources as well as stacks are moved to the FAILED state. Consequently, they can be recovered as expected upon restart of heat-engine.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-18 16:40:30 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
Zane Bitter
2015-09-29 19:24:34 UTC
It seems that reset_stack_status method ignores nested stacks (thanks Zane), after replacing: stacks = stack_object.Stack.get_all(cnxt, filters=filters, tenant_safe=False) or [] with: stacks = stack_object.Stack.get_all(cnxt, filters=filters, tenant_safe=False, show_nested=True) or [] All stacks are set to FAILED state after engine restart. Unfortunately this is not sufficient because resources remain in IN_PROGRESS state. It would be probably best to set them into FAILED state when stack is FAILED too. I have hit the same error too recently, I tend to think that this bug was exposed by some other bug fix because from what I was able to run package update on failed stacks before without needing to even restart heat engine (IOW stack didn't remain in IN_PROGRESS state). It turns out the part about resetting the resource states is already fixed upstream in Liberty. 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:2076 |