Bug 1400572

Summary: Ganesha services are not stopped when pacemaker quorum is lost
Product: [Community] GlusterFS Reporter: Kaleb KEITHLEY <kkeithle>
Component: common-haAssignee: Kaleb KEITHLEY <kkeithle>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.9CC: aloganat, amukherj, bugs, dang, ffilz, jthottan, mbenjamin, rhinduja, rhs-bugs, skoduri, storage-qa-internal
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.9.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1400237
: 1400573 (view as bug list) Environment:
Last Closed: 2017-02-21 11:25:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1399757, 1400237    
Bug Blocks: 1400573    

Comment 1 Worker Ant 2016-12-01 15:28:17 UTC
REVIEW: http://review.gluster.org/15996 (common-ha: IPaddr RA is not stopped when pacemaker quorum is lost) posted (#2) for review on release-3.9 by Kaleb KEITHLEY (kkeithle)

Comment 2 Worker Ant 2016-12-02 09:53:54 UTC
COMMIT: http://review.gluster.org/15996 committed in release-3.9 by Kaleb KEITHLEY (kkeithle) 
------
commit 07179c8188152d53e6be2c892bd24f3d8e6b70ea
Author: Kaleb S. KEITHLEY <kkeithle>
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>
    Reviewed-on: http://review.gluster.org/15996
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Kaushal 2017-03-08 10:20:58 UTC
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.9.1, please open a new bug report.

glusterfs-3.9.1 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://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html
[2] https://www.gluster.org/pipermail/gluster-users/