Bug 1850078

Summary: SBD does not work properly with new no-quorum-policy="demote" in pacemaker
Product: Red Hat Enterprise Linux 8 Reporter: Chris Feist <cfeist>
Component: sbdAssignee: Klaus Wenninger <kwenning>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 8.3CC: cfeist, cluster-maint, mmazoure, nhostako
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 04:09:20 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 Chris Feist 2020-06-23 13:56:54 UTC
Description of problem:
SBD does not work properly with new on-fail="demote" option in pacemaker

Comment 1 Klaus Wenninger 2020-06-23 14:34:11 UTC
no-quorum-policy="demote" comes with new on-fail="demote"

Binary resulting from current SBD-code (built against pacemaker-code without the new
no-quorum-policy) will just do nothing in case of quorum-loss if no-quorum-policy="demote"
which of course implies apparent danger of split-brain in the cluster.

Depending on the configured handling of warnings compilers will probably refuse building
sbd against pacemaker if it has the ne no-quorum-policy.

To prevent similar issues in future it is probably safest for sbd to handle unknown
no-quorum-policy values like no_quorum_suicide.

Comment 3 Klaus Wenninger 2020-06-24 15:03:11 UTC
https://github.com/ClusterLabs/sbd/pull/111

Comment 9 errata-xmlrpc 2020-11-04 04:09:20 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 (sbd 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-2020:4822