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 1448773

Summary:	PE Restarts resources on remote nodes when the connection is recovered
Product:	Red Hat Enterprise Linux 7	Reporter:	Andrew Beekhof <abeekhof>
Component:	pacemaker	Assignee:	Andrew Beekhof <abeekhof>
Status:	CLOSED ERRATA	QA Contact:	Udi Shkalim <ushkalim>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.3	CC:	abeekhof, cfeist, cluster-maint, kgaillot, lmiksik, mkrcmari
Target Milestone:	rc
Target Release:	7.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pacemaker-1.1.16-12.el7	Doc Type:	Bug Fix
Doc Text:	Cause: Consequence: Pacemaker could unnecessarily restart resources running on a Pacemaker Remote node when the node's connection needed to be recovered. Fix: Result: Pacemaker now does not restart resources on a Pacemaker Remote node whose connection is being recovered, unless necessary.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 17:57:08 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:

Description Andrew Beekhof 2017-05-08 03:59:35 UTC

Description of problem:

PE Restarts resources on remote nodes when the connection is recovered

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

<= 7.4

How reproducible:

100%

Steps to Reproduce:
1. Grab 1st attachment from bug #1448772
2. crm_simulate -Sx {attachment}
3.

Actual results:

 * Resource action: galera          demote on galera-0
...
 * Resource action: galera          demote on galera-2
...
 * Resource action: galera          stop on galera-0
...
 * Resource action: galera          stop on galera-2
...
 * Resource action: galera          start on galera-2
 * Resource action: galera          start on galera-0


Expected results:

The galera resource (as opposed to the galera-N nodes) are left alone

Additional info:

Comment 2 Andrew Beekhof 2017-05-09 02:36:49 UTC

Just confirmed this was also the behaviour in 1.1.16

Comment 3 Ken Gaillot 2017-05-09 19:53:08 UTC

Confirmed that this behavior also occurs in both RHEL 7.3's 1.1.15-11.el7_3.4 and RHEL 6.8's 1.1.14-8.el6

Comment 4 Ken Gaillot 2017-05-26 23:33:06 UTC

Fixed by upstream commits bc9ba911 through 1d735f0

Comment 5 Andrew Beekhof 2017-06-08 23:26:41 UTC

This bug is critical for OSP 12 which heavily features remote nodes due to the containerization effort.  Therefore it seems appropriate that OSP QE take this on.

Re-requesting 'exception?'

Comment 8 Marian Krcmarik 2017-06-26 13:49:06 UTC

Output from provided reproducer:
 * Pseudo action:   messaging-1_stop_0
 * Pseudo action:   galera-0_stop_0
 * Pseudo action:   galera-2_stop_0
 * Resource action: messaging-1     start on controller-2
 * Resource action: galera-0        start on controller-2
 * Resource action: galera-2        start on controller-2
 * Resource action: rabbitmq        monitor=10000 on messaging-1
 * Resource action: galera          monitor=10000 on galera-2
 * Resource action: galera          monitor=10000 on galera-0
 * Resource action: messaging-1     monitor=20000 on controller-2
 * Resource action: galera-0        monitor=20000 on controller-2
 * Resource action: galera-2        monitor=20000 on controller-2

No demote action is being triggered - verified.

Comment 9 errata-xmlrpc 2017-08-01 17:57:08 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/RHEA-2017:1862