glusterfs.git/xlators/mgmt/glusterd, branch v3.9.0

Remove experimental translators

2016-11-14T05:27:04+00:00

Change-Id: Id645918fa236f1fc00ab5fa427f394e853c44bf8
BUG: 1389675
Signed-off-by: Kaushal M 
Reviewed-on: http://review.gluster.org/15750
Tested-by: Pranith Kumar Karampuri 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

glusterd/quota: upgrade quota.conf file during an upgrade

2016-11-11T10:11:36+00:00

Problem
=======
When quota is enabled on 3.6, it will have quota conf version in quota.conf
as v1.1. This node gets upgraded to 3.7 but it will still have quota conf
version as v1.1 until a quota enable/disable/set limit is initiated. When
this is not initiated and when this node tries to peer probe a node which
is a fresh install of 3.7 (which will have quota conf version as v1.2), then this
will result in "Peer rejected" state. This patch fixes the issue.

Solution
========
When an upgrade happens from 3.6 to 3.7, quota.conf file needs
to be modified as well. With 3.6, in quota.conf the version will be
v1.1 and it needs to be changed to v1.2 from 3.7. This is because in
3.7, inode quota feature is introduced. So when an op-version bumpup
happens quota.conf needs to be upgraded with quota conf version v1.2
and all the 16 byte uuid needs to be changed to 17 bytes uuid as well.

Previously, when the cluster version is upgraded to 3.7, the quota.conf
got upgraded as well. But, the upgradation was done only when quota
enable/disable/set limit is done. With this patch, the upgradation is done
during a cluster op version bump up as well.


>Reviewed-on: http://review.gluster.org/15352
>Tested-by: Atin Mukherjee 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Smoke: Gluster Build System 
>Reviewed-by: Atin Mukherjee 
>(cherry picked from commit 4b2cff614462508eef529c5d128e0974720e3f50)

Change-Id: Idb5ba29d3e1ea0e45c85d87c952c75da9e0f99f0
BUG: 1392718
Signed-off-by: Manikandan Selvaganesh 
Reviewed-on: http://review.gluster.org/15792
Tested-by: Atin Mukherjee 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Manikandan Selvaganesh 
CentOS-regression: Gluster Build System

snapshot: Fix for memory leaks in snapshot code path

2016-11-02T06:31:57+00:00

> Reviewed-on: http://review.gluster.org/15668
> NetBSD-regression: NetBSD Build System 
> CentOS-regression: Gluster Build System 
> Smoke: Gluster Build System 
> Reviewed-by: Rajesh Joseph 

(cherry picked from commit 48a4c4e525665115f7e8c478d3bf51764427378d)

Change-Id: Idc2cb16574d166e3c0ee1f7c3a485f1acb19fc8c
BUG: 1388350
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/15719
NetBSD-regression: NetBSD Build System 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Rajesh Joseph

glusterd: conditionally pass uuid for EVENT_PEER_CONNECT

2016-10-24T08:01:11+00:00

When a new node is probed, on the first RPC_CLNT_CONNECT peerctx->uuid is set to
NULL as the same is yet to be populated. However the subesquent (dis)connect
events would be carrying the valid UUIDs.

Solution is not to generate EVENT_PEER_CONNECT on a peer probe trigger as CLI is
already going to take care of generating the same.

>Reviewed-on: http://review.gluster.org/15678
>Smoke: Gluster Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: Samikshan Bairagya 
>NetBSD-regression: NetBSD Build System 

Change-Id: I2f0de054ca09f12013a6afdd8ee158c0307796b9
BUG: 1387564
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/15697
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System 
Reviewed-by: Samikshan Bairagya

cli, glusterd: Address issues in get-state cli output

2016-10-21T17:41:08+00:00

This fixes the following data points:
1. Volume type
2. Peer state
3. List of other hostnames for a peer
4. Data unit information for rebalance

The following data points are removed:
1. Mount options and filesystem types for bricks
2. global-option-version from list of global options

The following data points are added:
1. Replica Count
2. Tier type for bricks belonging to hot/cold tier

> Reviewed-on: http://review.gluster.org/15662
> Reviewed-by: mohammed rafi  kc 
> CentOS-regression: Gluster Build System 
> NetBSD-regression: NetBSD Build System 
> Smoke: Gluster Build System 
> Reviewed-by: Atin Mukherjee 

(cherry picked from commit daea58a51b70f80ab04f115e49f8bf8790b6046a)

Change-Id: I5011250e863fdc4929b203cdb345d79b2f16c6a5
BUG: 1387502
Signed-off-by: Samikshan Bairagya 
Reviewed-on: http://review.gluster.org/15696
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Atin Mukherjee

glusterd: set the brickinfo->port before spawning the bricks

2016-10-21T09:17:13+00:00

As of now, when glusterd spawns a brick process, post spawning, the brickinfo's
port is set. The side effect of this is it opens up an window where the
pmap_signin event can be initiated by the brick to glusterd and glusterd fails
to update signed_in flag since the brickinfo port is still 0 and the comparison
of port and brickinfo->port fails.

As a solution, set the brickinfo->port post pmap_registry_alloc and if the brick
spawn fails reset it to 0. This logic applies for rdma port too.

>Reviewed-on: http://review.gluster.org/15655
>Smoke: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: Samikshan Bairagya 
>Reviewed-by: Jeff Darcy 

Change-Id: I00a13d4c6d6809ebd19a972aa13e71ee5eac7e35
BUG: 1386338
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/15679
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Samikshan Bairagya

glusterd: enable default configurations post upgrade to >= 3.9.0 versions

2016-10-18T05:20:17+00:00

With 3.8.0 onwards volume options like nfs.disable, transport.address-family
have some default configuration value. If a volume was created pre upgrade to
3.8.0 or higher the default options are not set post upgrade. This patch takes
care of putting the default values in the op-version bump up workflow. However
these changes will only reflect from 3.9.0 onwards

>Reviewed-on: http://review.gluster.org/15568
>Reviewed-by: jiffin tony Thottan 
>CentOS-regression: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>Smoke: Gluster Build System 
>Reviewed-by: soumya k 
>Reviewed-by: Kaushal M 

Change-Id: I9a8d848cd08d87ddcb80dbeac27eaae097d9cbeb
BUG: 1385451
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/15652
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System 
Reviewed-by: jiffin tony Thottan

glusterd: fix return val in glusterd_op_volume_dict_uuid_to_hostname ()

2016-09-29T05:26:59+00:00

glusterd_op_volume_dict_uuid_to_hostname () ignores few dict_get_str failures
but doesn't reset the ret value to 0.

Reproducer steps:
1. Configure a volume and start it (gNFS has to be disabled)
2. gluster volume status

An warning log is observed with:
[MSGID: 106217] [glusterd-op-sm.c:4706:glusterd_op_modify_op_ctx] 0-management:
Failed uuid to hostname conversion
[2016-09-22 09:21:38.537533] W [MSGID: 106387]
[glusterd-op-sm.c:4812:glusterd_op_modify_op_ctx] 0-management: op_ctx
modification failed

>Reviewed-on: http://review.gluster.org/15547
>Smoke: Gluster Build System 
>CentOS-regression: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>Reviewed-by: Samikshan Bairagya 
>Reviewed-by: Kaushal M 

Change-Id: I1d3aa79304d83a9d5db1b7198773d8c2780e24a9
BUG: 1379287
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/15572
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Prashanth Pai

ganesha/glusterd : Correct the path for ganesha conf dir in Makefile

2016-09-17T10:44:00+00:00

The value for ganesha conf dir in Makefile.am is mistakenly entered as
following :
DCONFDIR=\"/$(runstatedir)/gluster/shared_storage/nfs-ganesha\"

Here value for runstatedir is seems to "NULL" which results wrong path
for ganesha configuration directory

Upstream reference :
> Change-Id: I0b7ebd8e2503de0cb79b601553c4405d0d1fd711
> BUG: 1355956
> Signed-off-by: Jiffin Tony Thottan 
> Reviewed-on: http://review.gluster.org/15355
> NetBSD-regression: NetBSD Build System 
> Reviewed-by: soumya k 
> Reviewed-by: Niels de Vos 
> CentOS-regression: Gluster Build System 
> Smoke: Gluster Build System 
> (cherry picked from commit 7e18e16f9f62ed95acded0fb3f2a8784087f59c0)

Change-Id: I0b7ebd8e2503de0cb79b601553c4405d0d1fd711
BUG: 1376874
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/15521
Reviewed-by: soumya k 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Atin Mukherjee

Tier: failing detach commit on detach failure and in-progress

2016-09-15T20:49:38+00:00

        back-port of: http://review.gluster.org/#/c/15438/

PROBLEM: if detach status has failed or if it remains in progress
we allow detach commit to happen. only detach force should
be allowed.

FIX: check the detach status for failure or inprogress and disallow
with the apt error message.

>Change-Id: Ib97d540fec67717bb55c18d133187c665cf69ef1
>BUG: 1374584
>Signed-off-by: hari gowtham 
>Reviewed-on: http://review.gluster.org/15438
>Smoke: Gluster Build System 
>Tested-by: hari gowtham 
>NetBSD-regression: NetBSD Build System 
>CentOS-regression: Gluster Build System 
>Reviewed-by: Dan Lambright 
>Tested-by: Dan Lambright 
Signed-off-by: hari gowtham 

Change-Id: I4f8c3859121ee0827df57348069a243a2502889a
BUG: 1375570
Reviewed-on: http://review.gluster.org/15493
Tested-by: hari gowtham 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Smoke: Gluster Build System 
Reviewed-by: Dan Lambright