Bug 1660147

Summary:	timeout-action triggered by sbd-daemon isn't configurable
Product:	Red Hat Enterprise Linux 8	Reporter:	Klaus Wenninger <kwenning>
Component:	sbd	Assignee:	Klaus Wenninger <kwenning>
Status:	CLOSED CURRENTRELEASE	QA Contact:	cluster-qe <cluster-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	cfeist, cluster-maint, fdinitto, mlisik, oalbrigt
Target Milestone:	rc
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sbd-1.3.1-18.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1660158 (view as bug list)		Environment:
Last Closed:	2019-06-14 01:20:16 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:
Bug Depends On:
Bug Blocks:	1660158, 1664828

Description Klaus Wenninger 2018-12-17 15:57:23 UTC

Description of problem:
With most hardware-watchdog-devices the action performed if the watchdog runs off  can be configured to reboot or poweroff.
There is a race between hardware-watchdog and timeout-handling inside sbd-daemon.
If sbd-daemon is first to detect the timeout it always triggers a reboot leading to undesired effects if the action configured with the hardware-watchdog is a poweroff.
If sbd is being used without a hardware-watchdog (watchdog-device in general - softdog would apply as well though no inconsistency can arise here as softdog doesn't support being configure to poweroff) it is thus not configurable at all which action should be performed in case of a timeout.

Version-Release number of selected component (if applicable):
1.3.1-17.el8

How reproducible:
100%

Steps to Reproduce:
1. configure sbd without watchdog-device and without a shared disk
2. configure 3-node cluster
3. disconnect one of the nodes from the cluster so that loss of quorum makes pacemaker-watcher stop triggering sbd-inquisitor

Actual results:
sbd-inquisitor triggers a reboot


Expected results:
sbd-inquisitor triggers action as specified by new config-variable SBD_TIMEOUT_ACTION


Additional info: