Bug 1288929 - service pacemaker_remote stop causes node to be fenced
Summary: service pacemaker_remote stop causes node to be fenced
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 7.3
Assignee: Ken Gaillot
QA Contact: Asaf Hirshberg
Steven J. Levine
Depends On: 1304771
Blocks: 1185030 1297564 1299348 1323259 1325009
TreeView+ depends on / blocked
Reported: 2015-12-07 03:37 UTC by Andrew Beekhof
Modified: 2016-11-03 18:57 UTC (History)
9 users (show)

Fixed In Version: pacemaker-1.1.15-1.2c148ac.git.el7
Doc Type: Release Note
Doc Text:
Graceful migration of resources when the *pacemaker_remote* service is stopped on an active Pacemaker Remote node If the *pacemaker_remote* service is stopped on an active Pacemaker Remote node, the cluster will gracefully migrate resources off the node before stopping the node. Previously, Pacemaker Remote nodes were fenced when the service was stopped (including by commands such as "yum update"), unless the node was first explicitly taken out of the cluster. Software upgrades and other routine maintenance procedures are now much easier to perform on Pacemaker Remote nodes. Note: All nodes in the cluster must be upgraded to a version supporting this feature before it can be used on any node.
Clone Of:
: 1297564 1299348 (view as bug list)
Last Closed: 2016-11-03 18:57:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2578 0 normal SHIPPED_LIVE Moderate: pacemaker security, bug fix, and enhancement update 2016-11-03 12:07:24 UTC

Description Andrew Beekhof 2015-12-07 03:37:24 UTC
Description of problem:

Graceful shutdown doesn't work

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

How reproducible:


Steps to Reproduce:
1. Run: service pacemaker_remote stop 

Actual results:


Expected results:

1. Contacts/notifies peer cluster
2. Peer cluster stops all services
3. Peer cluster tells pacemaker_remote it can shut down
4. Peer cluster recognises that the remote node was expected to shutdown

Additional info:

Esp. relevant for OSP upgrades

Comment 1 Raoul Scarazzini 2015-12-24 10:28:02 UTC
As a side note, and as a workaround, the sequence of the commands we are using to avoid fencing is this one:

1) Reboot the compute node from console
2) Do a nova stop <computenodeid> from the undercloud
3) Do a nova start <computenodeid> from the undercloud
4) Do a cycle like this on one of the controller:
$ while true; do sudo pcs resource cleanup overcloud-novacompute-0; sleep 5; done
from a controller node
5) Once the machine is up, stop the cycle from step 4

Comment 2 Ken Gaillot 2016-01-08 21:29:33 UTC
Fixed upstream as of commit da17fd0

Comment 4 Mike McCune 2016-03-28 22:52:26 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions

Comment 6 Asaf Hirshberg 2016-06-06 09:41:59 UTC
Verified on RHEL-OSP director 9.0 puddle - 2016-06-03.1

Using "systemctl stop pacemaker_remote.service" stopping the service and pacemaker change the status to stopped:
overcloud-novacompute-1	(ocf::pacemaker:remote):	Stopped

When using kill command the status is changed to FAILED and the compute is fenced:
overcloud-novacompute-1	(ocf::pacemaker:remote):	FAILED


Comment 7 Steven J. Levine 2016-08-12 16:57:38 UTC
I'm putting in the same doc text that we had for this feature for RHEL 6.8 for the release notes.

Comment 9 errata-xmlrpc 2016-11-03 18:57:31 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.


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