Bug 1299348 - service pacemaker_remote stop causes node to be fenced
service pacemaker_remote stop causes node to be fenced
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Ken Gaillot
: ZStream
Depends On: 1288929
  Show dependency treegraph
Reported: 2016-01-18 02:50 EST by Jan Kurik
Modified: 2016-02-16 06:18 EST (History)
11 users (show)

See Also:
Fixed In Version: pacemaker-1.1.13-10.el7_2.2
Doc Type: Enhancement
Doc Text:
The pacemaker_remote service can now be stopped on an active Pacemaker Remote node, and the cluster gracefully migrates resources off the node before stopping the node. Previously, Pacemaker Remote nodes had to be taken out of the cluster before stopping the pacemaker_remote service, either explicitly or implicitly by commands such as "yum update", otherwise the node was fenced. Now, software upgrades and other routine maintenance are significantly easier to perform on Pacemaker Remote nodes. Note that all nodes in the cluster must be upgraded to a version supporting this feature before the feature can be used on any node.
Story Points: ---
Clone Of: 1288929
Last Closed: 2016-02-16 06:18:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0216 normal SHIPPED_LIVE Pacemaker bug fix and enhancement update 2016-02-16 11:14:04 EST

  None (edit)
Description Jan Kurik 2016-01-18 02:50:34 EST
This bug has been copied from bug #1288929 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 4 Ken Gaillot 2016-01-18 13:29:33 EST
QA: reproducer is to configure a cluster with a Pacemaker Remote node, then run "systemctl stop pacemaker_remote" on the node while it is in the cluster.

Previously, the node would be fenced; now, all resources will be moved off the node and it will gracefully stop. This should work the same for remote nodes (configured with ocf:pacemaker:remote resource) and guest nodes (configured with remote-node= attribute on a VM resource).
Comment 7 Ken Gaillot 2016-01-25 16:51:53 EST
QA: I should have mentioned, that after a graceful stop, the cluster will immediately try to connect to the remote node again. If the remote node is not accepting connections again before the start timeout, the start will fail (and move on to another node if available, and potentially time out there, too). If start times out on all nodes, the cluster will stop trying to reconnect. If a failure-timeout has been configured for the start operation, it will begin retrying again after that time.

This is necessary because all remote connections must be initiated from the cluster side, so there is no way for a newly started remote node to signal the cluster it is available. This may be changed in the future, but for now, start failures are expected if the remote node is down for an extended time -- it is only the stopping that is graceful now.
Comment 12 Ken Gaillot 2016-01-26 19:44:52 EST
An issue in the implementation, with the symptom of a second stop hanging, was found, and fixed upstream as of commit 942efa4. An updated build has been added to the errata.
Comment 15 errata-xmlrpc 2016-02-16 06:18:20 EST
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.