1481140 – [GANESHA] pcs status shows all nodes in started state for ~15 mins even when hit "partition WITHOUT quorum" with IO's still resuming [rhel-7.4.z]

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 1481140 - [GANESHA] pcs status shows all nodes in started state for ~15 mins even when hit "partition WITHOUT quorum" with IO's still resuming [rhel-7.4.z]

Summary: [GANESHA] pcs status shows all nodes in started state for ~15 mins even when...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pacemaker
Sub Component:
Version:	7.4
Hardware:	Unspecified
OS:	Unspecified
Priority:	urgent
Severity:	urgent
Target Milestone:	rc
Target Release:	7.4
Assignee:	Ken Gaillot
QA Contact:	cluster-qe@redhat.com
Docs Contact:
URL:
Whiteboard:
Depends On:	1464068
Blocks:
TreeView+	depends on / blocked

Reported:	2017-08-14 08:25 UTC by Oneata Mircea Teodor
Modified:	2017-09-05 11:31 UTC (History)
CC List:	18 users (show)
Fixed In Version:	pacemaker-1.1.16-12.el7_4.1
Doc Type:	Bug Fix
Doc Text:	Previously, quorum loss did not trigger Pacemaker to recheck resource placement. As a consequence, in certain situations Pacemaker required a long time, up to the cluster recheck interval, before stopping resources after quorum loss. This happened only when several conditions were met: a node that was correctly shutting down dropped the cluster below the quorum; that node was not running any resources at the time; and a cluster transition was already in progress. With this update, Pacemaker always cancels the current transition when quorum is lost and recalculates resource placement immediately. As a result, the long delay no longer occurs.
Clone Of:	1464068
Environment:
Last Closed:	2017-09-05 11:31:54 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:2587	0	normal	SHIPPED_LIVE	pacemaker bug fix update	2017-09-05 15:20:01 UTC

Description Oneata Mircea Teodor 2017-08-14 08:25:26 UTC

This bug has been copied from bug #1464068 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 2 Ken Gaillot 2017-08-15 15:20:38 UTC

Testing procedure (from parent bug):

1. Configure a cluster of at least three nodes, one dummy resource that takes a long time to stop, and at least one other resource.

2. Stop enough nodes so that the cluster is one node away from losing quorum.

3. Put one of the remaining nodes in standby, and wait until it has no resources running on it.

4. Disable the dummy resource so that it initiates a stop, and before it complete the stop, shut down the standby node.

Before the change, the cluster will not stop the remaining resource(s) on the active node(s) until the next cluster-recheck-interval. After the change, the cluster will immediate stop all remaining resources.

Comment 6 errata-xmlrpc 2017-09-05 11:31:54 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, 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-2017:2587

Note You need to log in before you can comment on or make changes to this bug.