Bug 2182482

Summary: [BDI] Pacemaker resources left UNCLEAN after controller node failure
Product: Red Hat Enterprise Linux 9 Reporter: Klaus Wenninger <kwenning>
Component: pacemakerAssignee: Klaus Wenninger <kwenning>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: urgent Docs Contact: Steven J. Levine <slevine>
Priority: high    
Version: 9.3CC: cfeist, cluster-maint, jrehova, kgaillot, kwenning, lmiccini, matteo.panella, mjuricek, nwahl, rbruzzon, sbradley, slevine
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: 9.3Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: All   
Whiteboard:
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.
Story Points: ---
Clone Of: 2168633
: 2187424 2187425 2187426 (view as bug list) Environment:
Last Closed: 2023-11-07 08:23:06 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: 2.1.6
Embargoed:
Bug Depends On: 2168633    
Bug Blocks: 2187424, 2187425, 2187426    

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