[Bugs] [Bug 1400572] Ganesha services are not stopped when pacemaker quorum is lost
bugzilla at redhat.com
bugzilla at redhat.com
Thu Dec 1 15:28:17 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1400572
--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15996 committed in release-3.9 by Kaleb
KEITHLEY (kkeithle at redhat.com)
------
commit 07179c8188152d53e6be2c892bd24f3d8e6b70ea
Author: Kaleb S. KEITHLEY <kkeithle at redhat.com>
Date: Thu Dec 1 09:31:38 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/
Change-Id: I47fc7ee84fcd6ad52ccb776913511978a8d517b4
BUG: 1400572
Signed-off-by: Kaleb S. KEITHLEY <kkeithle at redhat.com>
Reviewed-on: http://review.gluster.org/15996
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=wkUTIjsRnA&a=cc_unsubscribe
More information about the Bugs
mailing list