glusterfs.git/extras/ganesha/scripts, branch v3.8.2

ganesha/scripts : delete nfs-ganesha folder from shared storage during clean up

2016-07-04T13:28:24+00:00

A directory named "nfs-ganesha" will be created inside shared storage when
'gluster nfs-ganesha enable' is executed. Similarly this directory should be
removed when 'gluster nfs-ganesha disable' is executed.

Upstream reference:
>Change-Id: Icc09b32010de07c9809e22aafbb2fd08a5c8252f
>BUG: 1349398
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/14782
>Smoke: Gluster Build System 
>Reviewed-by: Niels de Vos 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>(cherry picked from commit ec3ea75513347deb95960f49d58fc19478a7ad17)

Change-Id: Icc09b32010de07c9809e22aafbb2fd08a5c8252f
BUG: 1351154
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/14833
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY

common-ha: race/timing issue setting up cluster

2016-06-08T12:14:56+00:00

The ganesha_grace resource agent can start before the ganesha_mon
resource agent, with the result that the crm_attribute that
ganesha_grace expects to find has not been created yet.

This is never (never? Or just so rarely that it has never actually
been seen during development) seen with four nodes, but with just
two nodes it's very repeatable.

Note that when long (FQDN) names are used it is not unexpected to
see Failed Actions in the output of `pcs status`, e.g.:

* nfs-grace_monitor_5000 on node1.fully.qualified.domain.name.com
'unknown error' (1): call=20, status=complete, exitreason='none',
last-rc-change='Wed Jun  1 12:32:32 2016', queued=0ms, exec=0ms
* nfs-grace_monitor_5000 on node2.fully.qualified.domain.name.com
'unknown error' (1): call=18, status=complete, exitreason='none',
last-rc-change='Wed Jun  1 12:32:42 2016', queued=0ms, exec=0ms

and as long as all the ganesha_grace_clone and cluster_ip-1
resource agents are in Started state then this is okay.

backport master:
> http://review.gluster.org/14607
> BUG: 1341768

Change-Id: I726c9946ceb1ca92872b321612eb0f4c3cc039d8
BUG: 1341770
Signed-off-by: Kaleb S KEITHLEY 
Reviewed-on: http://review.gluster.org/14609
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: jiffin tony Thottan

ganesha: fix the shebang for the copy-export script

2016-05-30T14:36:27+00:00

Backport of:
> BUG: 1340488
> Change-Id: I22061a8b8bc0ea43da91e5b2904a27a674a004be
> Reviewed-on: http://review.gluster.org/14548
> Reported-by: Patrick Matthäi 
> Signed-off-by: Niels de Vos 

BUG: 1340487
Change-Id: I22061a8b8bc0ea43da91e5b2904a27a674a004be
Reported-by: Patrick Matthäi 
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/14550
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: jiffin tony Thottan

common-ha: wait for cluster to elect DC before accessing CIB

2016-05-24T09:36:16+00:00

access attempts, e.g. `pcs property set stonith-enabled=false`
will fail (or time out) if attempted "too early", i.e. before
the cluster has elected its DC.

see https://bugzilla.redhat.com/show_bug.cgi?id=1336947#c3 and
https://bugzilla.redhat.com/show_bug.cgi?id=1320740

Change-Id: Ifc0aa7ce652c1da339b9eb8fe17e40e8a09b1096
BUG: 1336947
Signed-off-by: Kaleb S KEITHLEY 
Reviewed-on: http://review.gluster.org/14427
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: soumya k 
Reviewed-by: jiffin tony Thottan

ganesha/scripts : Fixing refresh config in ganesha-ha.sh

2016-05-19T16:50:14+00:00

The change http://review.gluster.org/#/c/14225/ cause a regression
for refresh config funtion in ganesha-ha.sh due to a invalid usage
of awk arguement.

>Change-Id: Id5adfb12f99b29bdb3531773cd34bd67cfff8768
>BUG: 1333319
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/14325
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: Kaleb KEITHLEY 
>Smoke: Gluster Build System 
>Reviewed-by: Niels de Vos 
>(cherry picked from commit 8299ad374b2b93f123b29e0d411930733a372a04)

Change-Id: Id5adfb12f99b29bdb3531773cd34bd67cfff8768
BUG: 1336798
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/14420
Smoke: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Kaleb KEITHLEY 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

common-ha: stonith-enabled option set error in new pacemaker

2016-05-19T10:17:19+00:00

Setting the option too early results in an error in newer versions
of pacemaker. Postpone setting the option in order for it to succeed.

N.B. We do not use a fencing agent. Yes, we know this is "not supported."

Backport from mainline
> http://review.gluster.org/#/c/14404/
> BUG: 1336945
> Change-Id: I86953fdd67e6736294dbd2d0795611837188bd9d

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

NFS-Ganesha : Parse the Export_Id correctly for unexporting volume

2016-05-18T13:56:14+00:00

Currently export id parsed using "cut -d ' ' -f8" which might endup
in giving wrong value. In case of multiple space chracter, output
may differ. In this all those instance will replaced by awk call

Upstream reference :
>Change-Id: I60dea8ce116900da3c1fc9badf898e51183a2ca1
>BUG: 1333319
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/14225
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Kaleb KEITHLEY 
>(cherry picked from commit 5440bad91026f27399df51856176aef85c1fcf4d)

Change-Id: I60dea8ce116900da3c1fc9badf898e51183a2ca1
BUG: 1336798
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/14396
Smoke: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Kaleb KEITHLEY 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

glusterd-ganesha : copy ganesha export configuration files during reboot

2016-05-18T13:55:39+00:00

glusterd creates export conf file for ganesha using hook script during
volume start and ganesha_manage_export() for volume set command. But this
routine is not added in glusterd restart scenario.
Consider the following case, in a three node cluster a volume got exported
via ganesha while one of the node is offline(glusterd is not running).
When the node comes back online, that volume is not exported on that node
due to the above mentioned issue.
Also I have removed unused variables from glusterd_handle_ganesha_op()
For this patch to work pcs cluster should running on that be node.

Upstream reference
>Change-Id: I5b2312c2f3cef962b1f795b9f16c8f0a27f08ee5
>BUG: 1330097
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/14063
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Atin Mukherjee 
>(cherry picked from commit f71e2fa49af185779b9f43e146effd122d4e9da0)

Change-Id: I5b2312c2f3cef962b1f795b9f16c8f0a27f08ee5
BUG: 1336801
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/14397
Smoke: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Tested-by: Kaleb KEITHLEY 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

core: assorted typos and spelling mistakes reported by Debian lintian

2016-05-18T13:55:02+00:00

Also missing bang (!) in #!/bin/bash in shell scripts.

Backport of
> http://review.gluster.org/#/c/14398/
> BUG: 1336793
> Change-Id: I567a4be8f0f31f6285550f243fe802895f6bc43b

Change-Id: I003554daede9937a41010e085c74e77957c5c608
BUG: 1336794
Reported-by: Patrick Matthäi 
Signed-off-by: Kaleb S KEITHLEY 
Reviewed-on: http://review.gluster.org/14400
NetBSD-regression: NetBSD Build System 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System

common-ha: continuous grace_mon log messages in /var/log/messages

2016-04-28T10:19:50+00:00

messages are seen on RHEL6.x and RHEL7.1 and earlier versions of
pacemaker. (And RHEL7.2 with RHEL7.1 pacemaker packages.)

It's not possible to query attrd attributes in the older version,
only set/update/clear them. The messages come from invalid attempts
to query the attributes.

However it is possible to query crm attributes. The fix here is to
create a "shadow" crm attribute for the attrd attribute. Changes are
made to both, queries are made on the crm attribute.

(Resource Agents "follow" the attrd attribute using constraint locations,
so we must keep the attrd attribute.)

Change-Id: I84ac1a80673e528d98b67b7d5062e21dcf744d4a
BUG: 1324509
Signed-off-by: Kaleb S KEITHLEY 
Reviewed-on: http://review.gluster.org/13919
Reviewed-by: Niels de Vos 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: soumya k