d1681e
From 16d3a7d636d115c44516dc415b26d2c6d0d17424 Mon Sep 17 00:00:00 2001
d1681e
From: "Kaleb S. KEITHLEY" <kkeithle@redhat.com>
d1681e
Date: Tue, 13 Jun 2017 07:36:50 -0400
d1681e
Subject: [PATCH 64/74] common-ha: surviving ganesha.nfsd not put in grace on
d1681e
 fail-over
d1681e
d1681e
Behavior change is seen in new HA in RHEL 7.4 Beta. Up to now clone
d1681e
RAs have been created with "pcs resource create ... meta notify=true".
d1681e
Their notify method is invoked with pre-start or post-stop when one of
d1681e
the clone RAs is started or stopped.
d1681e
d1681e
In 7.4 Beta the notify method we observe that the notify method is not
d1681e
invoked when one of the clones is stopped (or started).
d1681e
d1681e
Ken Gaillot, one of the pacemaker devs, wrote:
d1681e
  With the above command, pcs puts the notify=true meta-attribute
d1681e
  on the primitive instead of the clone. Looking at the pcs help,
d1681e
  that seems expected (--clone notify=true would put it on the clone,
d1681e
  meta notify=true puts it on the primitive). If you drop the "meta"
d1681e
  above, I think it will work again.
d1681e
d1681e
And indeed his suggested fix does work on both RHEL 7.4 Beta and RHEL
d1681e
7.3 and presumably Fedora.
d1681e
d1681e
Change-Id: Idbb539f1366df6d39f77431c357dff4e53a2df6d
d1681e
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
d1681e
Reviewed-on: https://review.gluster.org/17534
d1681e
Smoke: Gluster Build System <jenkins@build.gluster.org>
d1681e
Reviewed-by: soumya k <skoduri@redhat.com>
d1681e
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
d1681e
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
d1681e
---
d1681e
 extras/ganesha/scripts/ganesha-ha.sh | 2 +-
d1681e
 1 file changed, 1 insertion(+), 1 deletion(-)
d1681e
d1681e
diff --git a/extras/ganesha/scripts/ganesha-ha.sh b/extras/ganesha/scripts/ganesha-ha.sh
d1681e
index 0e4d23a..ce5ff20 100644
d1681e
--- a/extras/ganesha/scripts/ganesha-ha.sh
d1681e
+++ b/extras/ganesha/scripts/ganesha-ha.sh
d1681e
@@ -445,7 +445,7 @@ setup_create_resources()
d1681e
     # ganesha-active crm_attribute
d1681e
     sleep 5
d1681e
 
d1681e
-    pcs resource create nfs-grace ocf:heartbeat:ganesha_grace --clone meta notify=true
d1681e
+    pcs resource create nfs-grace ocf:heartbeat:ganesha_grace --clone notify=true
d1681e
     if [ $? -ne 0 ]; then
d1681e
         logger "warning: pcs resource create nfs-grace ocf:heartbeat:ganesha_grace --clone failed"
d1681e
     fi
d1681e
-- 
d1681e
1.8.3.1
d1681e