glusterfs.git/extras/ganesha/scripts/ganesha-ha.sh, branch v3.10.2

ganesha : minor improvments for commit e91cdf4 (17081)

2017-05-03T22:35:56+00:00

Change-Id: I3af13e081c5e46cc6f2c132e7a5106ac3355c850
BUG: 1443490
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/17152
Smoke: Gluster Build System 
Reviewed-by: soumya k 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

ganesha : allow refresh-config and volume export/unexport in failover state

2017-04-24T10:33:51+00:00

If ganesha is not running on one of nodes in HA cluster, then alli dbus
commands send to that ganesha server will fail. This results in both
refresh-config and volume export/unepxort failure. This change will
gracefully handle those scenarios.

Change-Id: I3f1b7b7ca98e54c273c266e56357d8e24dd1b14b
BUG: 1443490
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/17081
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: soumya k 
Reviewed-by: Kaleb KEITHLEY

common-ha: Use UpdateExports dbus msg for refresh-config

2017-04-24T10:33:28+00:00

In nfs-ganesha 2.4, new dbs msg type "UpdateExports" support
has been added. With this support, the exports can be re-configured
dynamically without the need to re-export the entries.

Note : This change was of part of 3.10 branching, but the commit 142ee0c
overwrites this patch. Hence resubmitting this change
Upstream reference :
>Change-Id: Iee7330d33e91db1126974a2ff46becb3764f2e5e
>BUG: 1382258
>Author:    Soumya Koduri 
>Reviewed-on: http://review.gluster.org/15617
>Smoke: Gluster Build System 
>CentOS-regression: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>Reviewed-by: Kaleb KEITHLEY 

Change-Id: Iee7330d33e91db1126974a2ff46becb3764f2e5e
BUG: 1443478
Author:    Soumya Koduri 
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/17080
Smoke: Gluster Build System 
Reviewed-by: soumya k 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

ganesha/scripts : Stop ganesha process on all nodes if cluster setup fails

2017-04-24T10:32:39+00:00

During staging phase of volume option "nfs-ganesha", symlink "ganesha.conf"
will be created plus ganesha process will be started. The cluster setup
happens during commit phase of that option. So if cluster set up fails, the
ganesha process will be running on all cluster nodes.

Change-Id: Ib2cb85364b7ef5b702acb4826ffdf8e6f31a2acd
BUG: 1426156
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/16823
Smoke: Gluster Build System 
Tested-by: Kaleb KEITHLEY 
Reviewed-by: soumya k 
Reviewed-by: Kaleb KEITHLEY 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

ganesha/scripts : Remove export entries from ganesha.conf during cleanup

2017-04-24T10:30:54+00:00

Change-Id: I288f7c9ced23d258a7ce1242d8efe03a4bf6f746
BUG: 1425726
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/16708
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: soumya k 
Reviewed-by: Kaleb KEITHLEY

common-ha: fixes for Debian-based systems

2017-04-13T15:37:57+00:00

1) Debian-based systems don't have /usr/libexec/... and there is
a hard-coded invocation of /usr/libexec/ganesha/ganesha-ha.sh within
ganesha-ha.sh itself.
Fix: save $0 and use it instead for further invocations of self.

2) default shell is /bin/dash (not /bin/bash). Various runner_run()
invocations for ganesha used what amounts to
  exec("sh /usr/$libexec/ganesha/ganesha-ha.sh ...);
which executes the script using the default shell, but there are
some bash-specific idioms that don't work if the shell is dash.
Fix: change to exec("/usr/$libexec/ganesha/ganesha-ha.sh ...); so that
the shebang forces the use of /bin/bash

3) Fedora and RHEL7 have merged /bin/ and /usr/bin, /bin is a symlink
to /usr/bin. Debian-based systems are not merged, and systemd systems
have /bin/systemctl. The logic to find .../bin/systemctl is backwards.
If the logic looks for /usr/bin/systemctl it will not find it on
Debian-based systems; if it looks for /bin/systemctl it will find it
on Fedora and RHEL by virtue of the symlink. (RHEL6 and others will
find their respective init regardless.)
Fix: change the logic to look for /bin/systemctl instead.

4) The logic for deciding to run systemctl (or not) is a bit silly.
Fix: simply invoke the found method via the function pointer in the
table.

Change-Id: I33681b296a73aebb078bda6ac0d3a1d3b9770a21
BUG: 1440148
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/17013
Smoke: Gluster Build System 
Reviewed-by: Niels de Vos 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: jiffin tony Thottan

common-ha: no need to remove nodes one-by-one in teardown

2017-02-26T19:13:06+00:00

`pcs cluster destroy --all` does all that's necessary, and prevents
`pcs cluster setup ...` from failing the next time a cluster is set up

This appears to happen when all the pacemaker and corosync files aren't
deleted on the other nodes in the cluster.

per Tomas Jelinek in IRC#cluster

Change-Id: Iff24e3732f91f3b96a0b00b8199aa42446e60938
BUG: 1426323
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/16737
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: soumya k 
CentOS-regression: Gluster Build System

ganesha/scripts : restart pcs cluster during add node

2017-02-23T15:27:15+00:00

In RHEL 6 due to this change https://review.gluster.org/#/c/16122/
restart of HA cluster become requirement after adding a node to
cluster
After add node "pcs cluster node add " following message is
coming up :
Warning: Using udpu transport on a RHEL 6 cluster, cluster restart is required to apply node addition

Thanks Manisha for founding issue and suggesting the fix.

Change-Id: I9e55d4ba04ed2555d27f26f71b95b8bd6a67f94c
BUG: 1425919
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/16721
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Tested-by: Kaleb KEITHLEY 
Reviewed-by: soumya k 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

common-ha: revert switch to storhaug

2017-02-20T23:21:27+00:00

we'll try again for 3.11.

Change-Id: Ib4c50414dc3d16a23dc7a49020445129da55843c
BUG: 1410843
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/16692
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Shyamsundar Ranganathan

storhaug HA: first step, remove resource agents and setup script

2017-01-18T00:53:30+00:00

resource agents and setup script(s) are now in storhaug

This is a phased switch-over to storhaug. Ultimately all components
here should be (re)moved to the storhaug project and its packages.
But for now some will linger here.

Change-Id: Ied3956972b14b14d8a76e22c583b1fe25869f8e7
BUG: 1410843
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/16349
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System