glusterfs.git/extras, branch v3.8.7

ganesha/scripts : use export id for dbus signals

2016-12-05T07:03:13+00:00

Currently for add export and update export parameter passed for executing those signal
is "PATH". This is based on assumption that volume name and PATH will always be same.
But it is wrong for subdir exports. The only reliable parameter in export configuration
file is "Export_Id".

Upstream reference :
>Change-Id: Ic63ff44ac7736e14502034b74beaae27292eddf9
>BUG: 1389746
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/15751
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Kaleb KEITHLEY 

Change-Id: Ic63ff44ac7736e14502034b74beaae27292eddf9
BUG: 1399635
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/15970
Smoke: Gluster Build System 
Reviewed-by: soumya k 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Kaleb KEITHLEY

common-ha: IPaddr RA is not stopped when pacemaker quorum is lost

2016-12-02T09:54:03+00:00

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 
Reviewed-on: http://review.gluster.org/15997
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

common-ha: add cluster HA status to --status output for gdeploy

2016-12-01T20:40:34+00:00

gdeploy desires a one-liner "health" assessment.

If all the VIP and port block/unblock RAs are located on their
prefered nodes and 'Started', then the cluster is deemed to be
good (healthy).

N.B. status originally only checked the "online" nodes obtained
from `pcs status` but we really want to consider all the configured
nodes, whether they are online or not.

Also one `pcs status` is enough.

master http://review.gluster.org/15882
master bug 1395648
release-3.9 http://review.gluster.org/15991
release-3.9 bug 1395649

Change-Id: Id0e0380b6982e23763edeb0488843b5363e370b8
BUG: 1395652
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-by: Arthy Loganathan 
Reviewed-by: soumya k 
Reviewed-on: http://review.gluster.org/15992
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

common-ha: nfs-grace-monitor timed out unknown error messages

2016-11-16T10:27:05+00:00

grace_mon_monitor() occasionally returns OCF_ERR_GENERIC, but it
ought to return OCF_NOT_RUNNING instead.

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

common-ha: remove /etc/corosync/corosync.conf in teardown/cleanup

2016-11-15T19:45:26+00:00

In newer versions of corosync we observe that after tearing down an
existing HA cluster, when trying to set up a new cluster, `pcs cluster
start --all` will fail if corosync believes the nodes are already in
the cluster based on the presence of, and the contents of
/etc/corosync/corosync.conf

So we summarily delete it. (An alternative/work-around is to use `pcs
cluster start --force --all`)

Change-Id: I225f4e35e3b605e860ec4f9537c40ed94ac68625
BUG: 1394883
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/15845
Smoke: Gluster Build System 
Reviewed-by: soumya k 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

common-ha: ganesha_mon: line 137: [: too many arguments ]" messages

2016-09-07T11:49:17+00:00

ensure that there are always valid, non-null arguments to /bin/test

Here there be dragons. Very racy, but if the races lose, they lose
in a way that's consistent with what we're testing for anyway, namely
that the ganesha.nfsd process is gone.

Change-Id: I88b770dd874ffa8576711f8009f27122a4fb0130
BUG: 1372728
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: http://review.gluster.org/15409
Reviewed-by: Niels de Vos 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Smoke: Gluster Build System

build: systemd unit should not be marked executable

2016-08-09T14:59:41+00:00

systemd complains about the unit for GlusterD when it is executable:

  Configuration file /usr/lib/systemd/system/glusterd.service is marked executable. Please remove executable permission bits. Proceeding anyway.

The Makefile that installs the unit has some scripted commands. These
are not needed and standard "*dir" and "*DATA" postfixes for variables
can be used instead.

The EXTRA_DIST variable is needed for building the 'make dist' tarball
on systems where there is no systemd. The unit would be missing from the
tarball if it is not explicitly included.

Cherry picked from commit 9f22282795e20fd62b22847b92dffd0cde9cca1b:
> BUG: 1354489
> Change-Id: I5e72ec201036906b9b2458bc8931ccebf9a8c6b4
> Reported-by: Sergej Pupykin 
> Signed-off-by: Niels de Vos 
> Reviewed-on: http://review.gluster.org/14892
> Smoke: Gluster Build System 
> Reviewed-by: Kaleb KEITHLEY 
> NetBSD-regression: NetBSD Build System 
> CentOS-regression: Gluster Build System 

Change-Id: I5e72ec201036906b9b2458bc8931ccebf9a8c6b4
BUG: 1354499
Reported-by: Sergej Pupykin 
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/15115
Smoke: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

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