REVIEW: http://review.gluster.org/15997 (common-ha: IPaddr RA is not stopped when pacemaker quorum is lost) posted (#2) for review on release-3.8 by Kaleb KEITHLEY (kkeithle)
COMMIT: http://review.gluster.org/15997 committed in release-3.8 by Kaleb KEITHLEY (kkeithle) ------ commit 377c3a00e2137c98fa4ffe52460dc17c8f2f8606 Author: Kaleb S. KEITHLEY <kkeithle> Date: Thu Dec 1 09:40:33 2016 -0500 common-ha: IPaddr RA is not stopped when pacemaker quorum is lost Ken Gaillot writes: The other is pacemaker's no-quorum-policy cluster property. The default (which has not changed) is "stop" (stop all resources). Other values are "ignore" (act as if quorum was not lost), "freeze" (continue running existing resources but don't recover resources from unseen nodes) or "suicide" (shut down). But on my four node cluster % pcs property show no-quorum-policy Cluster Properties: % i.e. shows nothing. But: % pcs property list --all Cluster Properties: ... no-quorum-policy: stop ... % Seems to think it knows about it. and then % pcs property set no-quorum-policy=stop % pcs property show no-quorum-policy Cluster Properties: no-quorum-policy: stop % Which looks rather inconsistent. So we will try explicitly setting it to "stop" when there are three or more nodes. master bug 1400237 master patch http://review.gluster.org/#/c/15981/ release-3.9 bug 1400527 release-3.9 patch http://review.gluster.org/15996 Change-Id: I47fc7ee84fcd6ad52ccb776913511978a8d517b4 BUG: 1400573 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: http://review.gluster.org/15997 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.7, please open a new bug report. glusterfs-3.8.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://www.gluster.org/pipermail/packaging/2016-December/000226.html [2] https://www.gluster.org/pipermail/gluster-users/
REVIEW: http://review.gluster.org/16247 (common-ha: IPaddr RA is not stopped when pacemaker quorum is lost) posted (#1) for review on release-3.8-fb by Kevin Vigor (kvigor)