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 1566533

Summary:	pacemaker can get in a state where a remote is unable to connect to the cluster [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:	pkomarov
Severity:	urgent	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	urgent
Version:	7.5	CC:	abeekhof, aherr, cluster-maint, kgaillot, michele, mjuricek, mkrcmari, oblaut, sbradley
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	7.5
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	pacemaker-1.1.18-11.el7_5.1	Doc Type:	Bug Fix
Doc Text:	In certain situations, Pacemaker cleared the fail counter of a remote node before the node was successfully fenced. Thus, a subsequent reconnect failed when the attempt was tried between error cleaning and the actual fencing. A very low value set in the reconnect_interval option increased the chance of this situation. Consequently, Pacemaker was unable to reconnect to the remote host. With this update, Pacemaker now delays resource failure time outs until pending fencing actions are completed. As a result, the described scenario no longer appears and remote nodes are correctly recovered.	Story Points:	---
Clone Of:	1565187	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:	1565187
Bug Blocks:

Description Oneata Mircea Teodor 2018-04-12 13:26:10 UTC

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

Comment 5 pkomarov 2018-04-24 10:51:47 UTC

Verified , 

Tested cluster integrity on all nodes after compute failover

environment details : 

pacemaker-libs-1.1.18-11.el7.x86_64

osp13 core_puddle_version:2018-04-19.2

With instance-ha deployed .

Comment 8 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