Bug 2092950
Summary: | pcs resource manage --monitor enables monitor for all resources in a group | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Tomas Jelinek <tojeline> |
Component: | pcs | Assignee: | Tomas Jelinek <tojeline> |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
Severity: | medium | Docs Contact: | Steven J. Levine <slevine> |
Priority: | medium | ||
Version: | 9.0 | CC: | cluster-maint, cluster-qe, idevat, mlisik, mmazoure, mpospisi, nhostako, nwahl, omular, sbradley, slevine, tojeline |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 9.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | pcs-0.11.3-5.el9 | Doc Type: | Bug Fix |
Doc Text: |
.Enabling a single resource and monitoring operation no longer enables monitoring operations for all resources in a resource group
Previously, after unmanaging all resources and monitoring operations in a resource group, managing one of the resources in that group along with its monitoring operation re-enabled the monitoring operations for all resources in the resource group. This could trigger unexpected cluster behavior.
With this fix, managing a resource and re-enabling its monitoring operation re-enables the monitoring operation for that resource only and not for the other resources in a resource group.
|
Story Points: | --- |
Clone Of: | 1918527 | Environment: | |
Last Closed: | 2023-05-09 07:18:23 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
Tomas Jelinek
2022-06-02 15:27:07 UTC
Upstream fix + tests: https://github.com/ClusterLabs/pcs/commit/ddbd11f255702a171ddbfc84cd219adce4e0ea7b Test: See Steps to Reproduce, Actual results, Expected results in comment 0 DevTestResults: [root@r92-1 ~]# rpm -q pcs pcs-0.11.3-5.el9.x86_64 [root@r92-1 ~]# pcs resource * Resource Group: G: * d1 (ocf:pacemaker:Dummy): Started r92-1 * d2 (ocf:pacemaker:Dummy): Started r92-1 [root@r92-1 ~]# pcs resource unmanage --monitor d1 [root@r92-1 ~]# pcs resource unmanage --monitor d2 [root@r92-1 ~]# pcs resource * Resource Group: G: * d1 (ocf:pacemaker:Dummy): Started r92-1 (unmanaged) * d2 (ocf:pacemaker:Dummy): Started r92-1 (unmanaged) [root@r92-1 ~]# pcs resource manage --monitor d1 [root@r92-1 ~]# pcs resource * Resource Group: G: * d1 (ocf:pacemaker:Dummy): Started r92-1 * d2 (ocf:pacemaker:Dummy): Started r92-1 (unmanaged) The same test as in bz1918527 comment 10 was used to verify this bz. Marking as VERIFIED for pcs-0.11.4-4.el9. 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 (pcs 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-2023:2151 |