[Bugs] [Bug 1400573] Ganesha services are not stopped when pacemaker quorum is lost

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1400573



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15997 committed in release-3.8 by Kaleb
KEITHLEY (kkeithle at redhat.com) 
------
commit 377c3a00e2137c98fa4ffe52460dc17c8f2f8606
Author: Kaleb S. KEITHLEY <kkeithle at redhat.com>
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 at redhat.com>
    Reviewed-on: http://review.gluster.org/15997
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.