glusterfs.git/extras, branch release-3.10

common-ha/scripts : pass the list of servers properly to stop_ganesha_all()

2018-04-04T04:05:00+00:00

Change-Id: I6d92623cd9fb450d7a27f5acc61eca0b3cbc9b08
BUG: 1563500
Signed-off-by: Jiffin Tony Thottan

glusterd : introduce timer in mgmt_v3_lock

2018-03-20T13:58:38+00:00

Problem:
In a multinode environment, if two of the op-sm transactions
are initiated on one of the receiver nodes at the same time,
there might be a possibility that glusterd  may end up in
stale lock.

Solution:
During mgmt_v3_lock a registration is made to  gf_timer_call_after
which release the lock after certain period of time

>Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843
>BUG: 1499004
>Signed-off-by: Gaurav Yadav 

Change-Id: I16cc2e5186a2e8a5e35eca2468b031811e093843
BUG: 1557304
Signed-off-by: Gaurav Yadav

glusterd: Gluster should keep PID file in correct location

2017-10-25T14:03:54+00:00

Currently Gluster keeps process pid information of all the daemons
and brick processes in Gluster configuration file directory
(ie., /var/lib/glusterd/*).

These pid files should be seperate from configuration files.
Deletion of the configuration file directory might result into serious problems.
Also, /var/run/gluster is the default placeholder directory for pid files.

So, with this fix Gluster will keep all process pid information of all
processes in /var/run/gluster/* directory.

> Change-Id: Idb09e3fccb6a7355fbac1df31082637c8d7ab5b4
> BUG: 1258561
> Signed-off-by: Gaurav Kumar Garg 
> Signed-off-by: Saravanakumar Arumugam 
> Reviewed-on: https://review.gluster.org/13580
> Tested-by: MOHIT AGRAWAL 
> Smoke: Gluster Build System 
> CentOS-regression: Gluster Build System 
> Reviewed-by: Atin Mukherjee 
> (Cherry pick from commit 220d406ad13d840e950eef001a2b36f87570058d)

BUG: 1491059
Change-Id: Idb09e3fccb6a7355fbac1df31082637c8d7ab5b4
Signed-off-by: Mohit Agrawal

ganesha-ha: don't set SELinux booleans if SELinux is disabled

2017-09-16T13:01:48+00:00

semanage commands inside ganesha-ha.sh script will fail if selinux is
Disabled. This patch introduces a check if selinux is enabled or not,
and subsequently run semange commands only on selinux enabled systems.

Change-Id: Ibee61cbb1d51a73e6c326b49bac5c7ce06feb310
BUG: 1490909
Signed-off-by: Ambarish 
Reviewed-on: https://review.gluster.org/18264
Reviewed-by: Niels de Vos 
Smoke: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: jiffin tony Thottan 
Reviewed-by: Daniel Gryniewicz 
CentOS-regression: Gluster Build System

scripts: invalid test(1) in extras/S32gluster_enable_shared_storage.sh

2017-08-11T10:54:31+00:00

test(1) man pages says -eq is for INTEGER compares, and = is for
string compares.

Also note the comment that -a and -o are ambiguous and to use
test && test or test || test instead.

This bug has existed since 2015! (yikes)

Found while testing localtime logging and running glusterd in the
foreground.

Change-Id: Ia544f7295e247b981504d085ebc4c533ab60ba84
BUG: 1478498
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/17978
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Nigel Babu

common-ha: enable and disable selinux gluster_use_execmem

2017-07-28T12:28:41+00:00

Starting in Fedora 26 and RHEL 7.4 there are new targeted policies in
selinux which include a tuneable to allow glusterd->ganesha-ha.sh->pcs
to access the pcs config, i.e. gluster-use-execmem.

Note. rpm doesn't have a way to distinguish between RHEL 7.3 or 7.4
or between 3.13.1-X and 3.13.1-Y so it can't be enabled for RHEL at
this time.

/usr/sbin/semanage is in policycoreutils-python in RHEL (versus
policycoreutils-python-utils in Fedora.)

Requires selinux-policy >= 3.13.1-160 in RHEL7. The corresponding
version in Fedora 26 seems to be selinux-policy-3.13.1-259 or so. (Maybe
earlier versions, but that's what was in F26 when I checked.)

Change-Id: Ic474b3f7739ff5be1e99d94d00b55caae4ceb5a0
BUG: 1471917
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/17806
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: soumya k 
Reviewed-by: Atin Mukherjee

common-ha: surviving ganesha.nfsd not put in grace on fail-over

2017-06-14T11:46:35+00:00

Behavior change is seen in new HA in RHEL 7.4 Beta. Up to now clone
RAs have been created with "pcs resource create ... meta notify=true".
Their notify method is invoked with pre-start or post-stop when one of
the clone RAs is started or stopped.

In 7.4 Beta the notify method we observe that the notify method is not
invoked when one of the clones is stopped (or started).

Ken Gaillot, one of the pacemaker devs, wrote:
  With the above command, pcs puts the notify=true meta-attribute
  on the primitive instead of the clone. Looking at the pcs help,
  that seems expected (--clone notify=true would put it on the clone,
  meta notify=true puts it on the primitive). If you drop the "meta"
  above, I think it will work again.

And indeed his suggested fix does work on both RHEL 7.4 Beta and RHEL
7.3 and presumably Fedora.

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

common-ha: adding a node to existing cluster failed to start pacemaker

2017-05-17T09:33:56+00:00

`pcs cluster start` in add_node() needs to wait for SSL certs to
propagate, etc. -- just like setup.

Change-Id: I44876305630a82e471824c085ed9ac58df08caa2
BUG: 1450053
Signed-off-by: Kaleb S. KEITHLEY 
Reviewed-on: https://review.gluster.org/17255
Reviewed-by: soumya k 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: jiffin tony Thottan

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/scripts : remove dependency over export configuration file for unexport

2017-05-01T21:44:23+00:00

Currently unexport is performed by reading export id from volume configuration
file. So unexport has dependency over that file. This patch will unexport with
help of dbus command ShowExport. And it will only unexport the share which is
added via cli.

Change-Id: I6f3c9b2bb48f0328b18e9cc0e4b9356174afd596
BUG: 1427079
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: https://review.gluster.org/16771
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Raghavendra Talur