RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1951098 - crm_mon not able to detect resource-status when used in stop-operation of a Resource Agent during node shutdown [rhel-8.4.0.z]
Summary: crm_mon not able to detect resource-status when used in stop-operation of a R...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.4
Hardware: All
OS: All
urgent
high
Target Milestone: rc
: ---
Assignee: Klaus Wenninger
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1948620
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-19 15:53 UTC by RHEL Program Management Team
Modified: 2021-05-26 07:05 UTC (History)
10 users (show)

Fixed In Version: pacemaker-2.0.5-9.el8_4.1
Doc Type: Bug Fix
Doc Text:
.The `ocf:heartbeat:pgsql` resource agent may fail to stop during a shutdown process in RHEL 8.4 In the RHEL 8.4 GA release, Pacemaker's `crm_mon` command-line tool was modified to display a "shutting down" message rather than the usual cluster information when Pacemaker starts to shut down. As a result, shutdown progress, such as the stopping of resources, can not be monitored, and resource agents that parse crm_mon output in their stop operation (such as the `ocf:heartbeat:pgsql` agent distributed with the resource-agents package, or some custom or third-party agents) could fail to stop, leading to cluster problems. It is recommended that clusters that use the `ocf:heartbeat:pgsql` resource agent not be upgraded to RHEL 8.4 until the z-stream is available.
Clone Of: 1948620
Environment:
Last Closed: 2021-05-18 18:59:43 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 6034771 0 None None None 2021-05-12 02:01:46 UTC

Comment 1 Ken Gaillot 2021-04-19 16:49:04 UTC
QA: reproducer is same as for parent bz, the minimum is:

1. Start a cluster with some resources that take long enough to stop to check pcs status while they're stopping.
2. Run "pcs cluster stop --all", and run "pcs status" on some node while the resources are stopping.
3. Before the fix, the status will just be "Pacemaker daemons shutting down ...". After the fix, it should show the resources stopping.

Comment 15 errata-xmlrpc 2021-05-18 18:59:43 UTC
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-2021:1996


Note You need to log in before you can comment on or make changes to this bug.