+++ This bug was initially created as a clone of Bug #1288929 +++
Description of problem:
Graceful shutdown doesn't work
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run: service pacemaker_remote stop
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
Esp. relevant for OSP upgrades
--- Additional comment from Raoul Scarazzini on 2015-12-24 05:28:02 EST ---
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
--- Additional comment from Ken Gaillot on 2016-01-08 16:29:33 EST ---
Fixed upstream as of commit da17fd0
QA on RHEL-7.2 z-stream with same fixes as used here found
some issues (see rhbz#1299348).
Fixed in Version: pacemaker-1.1.14-2.0.el6
Upstream commit cd10f0b is needed to support this feature on RHEL6 due to the use of legacy attrd, and will be backported
build has been updated
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.