Bug 1334467
| Summary: | [RFE] Mark Unhealthy Resources | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jaromir Coufal <jcoufal> |
| Component: | openstack-heat | Assignee: | Zane Bitter <zbitter> |
| Status: | CLOSED ERRATA | QA Contact: | Amit Ugol <augol> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9.0 (Mitaka) | CC: | ahmed.el-khouly, jdonohue, jjoyce, jschluet, mburns, mlopes, nlevinki, rhel-osp-director-maint, sbaker, shardy, srevivo |
| Target Milestone: | ga | Keywords: | FutureFeature, TestOnly, ZStream |
| Target Release: | 9.0 (Mitaka) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-heat-6.0.0-1.el7ost | Doc Type: | Enhancement |
| Doc Text: |
With this enhancement, you can mark a resource as unhealthy using an API call in Orchestration (heat), so that it will be replaced on a subsequent stack update.
For example, if a server in a `ResourceGroup` fails, rather than blacklisting (which would mean non-contiguous indices and any replacement getting a new name) the server can be marked unhealthy so that Heat will replace it with a new one with the same name and index in the group.
The new `mark-unhealthy` command allows a resource to be put in the CHECK_FAILED state. Any stack updates subsequently performed will replace the unhealthy resource (as they do with all resources in an *_FAILED state).
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-24 12:54:01 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: | |||
| Bug Depends On: | 1351429 | ||
| Bug Blocks: | 1243045, 1335634, 1362719 | ||
|
Description
Jaromir Coufal
2016-05-09 16:56:07 UTC
*** Bug 1268962 has been marked as a duplicate of this 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://rhn.redhat.com/errata/RHEA-2016-1761.html |