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 1563345

Summary:	Resource in Failed followed by Stopped status after a node failover [rhel-7.5.z]
Product:	Red Hat Enterprise Linux 7	Reporter:	Oneata Mircea Teodor <toneata>
Component:	pacemaker	Assignee:	Ken Gaillot <kgaillot>
Status:	CLOSED ERRATA	QA Contact:	Marian Krcmarik <mkrcmari>
Severity:	urgent	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	urgent
Version:	7.5	CC:	abeekhof, aherr, cfeist, cluster-maint, dciabrin, kgaillot, michele, mjuricek, mkrcmari
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	7.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pacemaker-1.1.18-11.el7_5.1	Doc Type:	Bug Fix
Doc Text:	Previously, Pacemaker scheduled notifications for clone actions which hadn't actually been run, but were just implied by fencing of the underlying node. In situations with a large number of such actions, these notifications led to long recovery times, saturation of the messaging mechanisms, loss of messages, and other consequential errors when using, for example, the bundle feature. Pacemaker no longer schedules notifications for implied events. As a result, recovery proceeds quickly after failure of a node hosting bundles with clone resources.	Story Points:	---
Clone Of:	1545449	Environment:
Last Closed:	2018-05-14 16:13:02 UTC	Type:	---
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:	1545449
Bug Blocks:

Description Oneata Mircea Teodor 2018-04-03 16:20:28 UTC

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

Comment 2 Ken Gaillot 2018-04-06 21:44:25 UTC

Fix 191c5be5 is in upstream 1.1 branch

Comment 3 Ken Gaillot 2018-04-06 22:57:00 UTC

Test packages with the fix are available at https://people.redhat.com/kgaillot/bz1563345/

Feedback is appreciated.

Comment 4 Damien Ciabrini 2018-04-18 12:30:10 UTC

Hey Ken, sorry for the delay

We did test the patch one day before your scratch build and that fixed our problem. We didn't re-run yet with your scratch build, but it seems at least we're good that the patch :)

Comment 5 Marian Krcmarik 2018-04-18 12:37:48 UTC

(In reply to Damien Ciabrini from comment #4)
> Hey Ken, sorry for the delay
> 
> We did test the patch one day before your scratch build and that fixed our
> problem. We didn't re-run yet with your scratch build, but it seems at least
> we're good that the patch :)

My apologies, the same here, I tested the scratch build and It did fix the issue I reported. Thanks!

Comment 10 errata-xmlrpc 2018-05-14 16:13:02 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-2018:1404