Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1703134

Summary:	sbd is affected by quorum-state-update delayed by way more than corosync-token-loss-timeout if qdevice is used
Product:	Red Hat Enterprise Linux 8	Reporter:	Klaus Wenninger <kwenning>
Component:	Documentation	Assignee:	Steven J. Levine <slevine>
Documentation sub component:	default	QA Contact:	RHEL DPM <rhel-docs>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	unspecified
Priority:	medium	CC:	cfeist, cluster-maint, cluster-qe, ctowsley, jfriesse, mmazoure, nwahl, rhel-docs, tojeline
Version:	8.0	Keywords:	Documentation
Target Milestone:	rc	Flags:	kwenning: needinfo- pm-rhel: mirror+
Target Release:	8.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1703128	Environment:
Last Closed:	2021-01-13 16:14:26 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:	1703128
Bug Blocks:

Description Klaus Wenninger 2019-04-25 15:20:23 UTC

+++ This bug was initially created as a clone of Bug #1703128 +++

Description of problem:

Before qdevice update of quorum-state was guaranteed to be more
or less immediate with a delay around corosync-token-loss-timeout
around 1s.
Sbd relies on quorum-state-update to arrive with a delay significantly
below watchdog-timeout.
This was covered with a default watchdog-timeout of 5s.
With qdevice quorum-state-update can be delayed up to 
quorum.device.sync_timeout defaulting to 30s.

Version-Release number of selected component (if applicable):

1.3.1-18

How reproducible:

If qdevice answer is delayed (e.g. artificially) the impact is 100%

Steps to Reproduce:
1. Setup 2-node-cluster with qdevice and sbd with watchdog-fencing (default watchdog-timeout = 5s)
2. Issue 'killall -STOP corosync-qdevice'
3. Separate one node from cluster
4. Wait a few seconds and verify (journalctl -f -u sbd) that node isn't rebooted due to quorum-loss
5. Issue 'killall -CONT corosync-qdevice'

Actual results:

Node just reboots short after SIGCONT.

Expected results:

Node should reboot after watchdog-timeout

Additional info:

Fix of bz1702727 already leads to a reboot after watchdog-timeout.
What we might like to see is that it is not possible to configure
watchdog-timeout < quorum.device.sync_timeout.
Or at least have documentation point us to not to do so.

Comment 1 Steven J. Levine 2019-06-28 18:44:48 UTC

Moving to 8.2 target release as per original BZ

Comment 3 Steven J. Levine 2019-11-27 19:22:24 UTC

Comment 1 was meant to go on the docs clone of this BZ, not on this BZ.

Comment 4 Steven J. Levine 2019-11-27 19:24:01 UTC

Forget comment 3.  I was confused that I was the assignee since this looked like a feature bug.