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.

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: