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 1992014 - Pacemaker fencer should retry failed meta-data commands [rhel-8.4.0.z]
Summary: Pacemaker fencer should retry failed meta-data commands [rhel-8.4.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pacemaker
Version: 8.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: beta
: ---
Assignee: Klaus Wenninger
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1797579
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-10 14:42 UTC by RHEL Program Management Team
Modified: 2022-09-13 15:11 UTC (History)
12 users (show)

Fixed In Version: pacemaker-2.0.5-9.el8_4.3
Doc Type: Bug Fix
Doc Text:
Cause: If a fence agent meta-data request fails, Pacemaker previously would consider that result final. While this would be the best response for a permanent issue such as a nonconforming agent, the failure could be transient, for example when Pacemaker is enabled at boot and heavy CPU and/or I/O load at boot causes the meta-data request to time out. Consequence: Pacemaker would not know if the fence agent supports unfencing or other optional features, and would act as if it did not, which could cause unfencing failures and other issues. Fix: If Pacemaker is unable to obtain fence agent meta-data on the first try, it will now periodically retry. Result: Although problems could still occur during a short time window, the meta-data will be obtained when feasible if the failure was transient, and the issues should be recoverable.
Clone Of: 1797579
Environment:
Last Closed: 2021-09-21 08:39:48 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-93041 0 None None None 2021-08-10 15:44:03 UTC
Red Hat Knowledge Base (Solution) 6534651 0 None None None 2022-09-13 15:11:25 UTC
Red Hat Product Errata RHBA-2021:3578 0 None None None 2021-09-21 08:39:54 UTC

Comment 1 Ken Gaillot 2021-08-10 16:11:13 UTC 
Fixed upstream as of commit 1d33712
Comment 9 errata-xmlrpc 2021-09-21 08:39:48 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:3578
Note You need to log in before you can comment on or make changes to this bug.