Bug 2065818
| Summary: | crm_resource --why should indicate when a resource is stopped due to a node's health | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Ken Gaillot <kgaillot> |
| Component: | pacemaker | Assignee: | Ken Gaillot <kgaillot> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.6 | CC: | cluster-maint, jrehova, msmazova, sbradley |
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
| Target Release: | 8.7 | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | pacemaker-2.1.4-4.el8 | Doc Type: | Enhancement |
| Doc Text: |
Feature: The crm_resource command's --why option, and pcs resource cleanup, now indicate when a resource remains stopped on a node due to the node's health being degraded.
Reason: If a user runs "pcs resource cleanup" for a resource, and the resource is still not running, it can be confusing as to what to look at next. The command would already indicate a few common conditions like the resource being disabled, but there would be no indication if the resource remained stopped because the node's health was degraded.
Result: It is now easier to tell what to investigate if a resource is stopped due to a node's health being degraded.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-08 09:42:30 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ken Gaillot
2022-03-18 19:46:14 UTC
Fixed in upstream main branch as of commit 6630e55 * 2-node cluster Version of pacemaker: > [root@virt-008 ~]# rpm -q pacemaker > pacemaker-2.1.4-4.el8.x86_64 Enabling node health monitoring: > [root@virt-008 ~]# pcs property set node-health-strategy="migrate-on-red" > [root@virt-008 ~]# pcs property > Cluster Properties: > cluster-infrastructure: corosync > cluster-name: STSRHTS26647 > dc-version: 2.1.4-4.el8-dc6eb4362e > have-watchdog: false > node-health-strategy: migrate-on-red Create a resource: > [root@virt-008 ~]# pcs resource create resource_dummy ocf:pacemaker:Dummy > [root@virt-008 ~]# pcs status > Cluster name: STSRHTS26647 > Cluster Summary: > * Stack: corosync > * Current DC: virt-008 (version 2.1.4-4.el8-dc6eb4362e) - partition with quorum > * Last updated: Wed Aug 3 16:58:06 2022 > * Last change: Wed Aug 3 16:58:00 2022 by root via cibadmin on virt-008 > * 2 nodes configured > * 3 resource instances configured > > Node List: > * Online: [ virt-008 virt-009 ] > > Full List of Resources: > * fence-virt-008 (stonith:fence_xvm): Started virt-008 > * fence-virt-009 (stonith:fence_xvm): Started virt-009 > * resource_dummy (ocf::pacemaker:Dummy): Started virt-008 > > Daemon Status: > corosync: active/disabled > pacemaker: active/disabled > pcsd: active/enabled Simulating a node health degraded condition: > [root@virt-008 ~]# pcs node attribute virt-008 '#health-test=red' Result message: > [root@virt-008 ~]# crm_resource --why --resource resource_dummy --node virt-008 > Resource resource_dummy is not running on host virt-008 > 'resource_dummy' cannot run on unhealthy nodes due to node-health-strategy='migrate-on-red' 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 (pacemaker bug fix and enhancement update), 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-2022:7573 |