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 2182482 - [BDI] Pacemaker resources left UNCLEAN after controller node failure
Summary: [BDI] Pacemaker resources left UNCLEAN after controller node failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pacemaker
Version: 9.3
Hardware: x86_64
OS: All
high
urgent
Target Milestone: rc
: 9.3
Assignee: Klaus Wenninger
QA Contact: cluster-qe
Steven J. Levine
URL:
Whiteboard:
Depends On: 2168633
Blocks: 2187424 2187425 2187426
TreeView+ depends on / blocked
 
Reported: 2023-03-28 19:42 UTC by Klaus Wenninger
Modified: 2023-11-07 08:57 UTC (History)
12 users (show)

Fixed In Version: pacemaker-2.1.6-1.el9
Doc Type: Bug Fix
Doc Text:
.A fence watchdog configured as a second fencing device now fences a node when the first device times out Previously, when a watchdog fencing device was configured as the second device in a fencing topology, the watchdog timeout would not be considered when calculating the timeout for the fencing operation. As a result, if the first device timed out the fencing operation would time out even though the watchdog would fence the node. With this fix, the watchdog timeout is included in the fencing operation timeout and the fencing operation succeeds if the first device times out.
Clone Of: 2168633
: 2187424 2187425 2187426 (view as bug list)
Environment:
Last Closed: 2023-11-07 08:23:06 UTC
Type: Bug
Target Upstream Version: 2.1.6
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-6700 0 None None None 2023-05-16 14:17:25 UTC
Red Hat Issue Tracker RHELPLAN-153340 0 None None None 2023-03-28 19:42:58 UTC
Red Hat Knowledge Base (Solution) 6997664 0 None None None 2023-03-28 20:01:09 UTC
Red Hat Product Errata RHEA-2023:6314 0 None None None 2023-11-07 08:23:51 UTC

Comment 15 errata-xmlrpc 2023-11-07 08:23:06 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/RHEA-2023:6314
Note You need to log in before you can comment on or make changes to this bug.