glusterfs.git/tests/bugs/glusterd, branch v3.7.3

glusterd: initialize the daemon services on demand

2015-07-27T14:31:30+00:00

Backport of http://review.gluster.org/#/c/11488/

As of now all the daemon services are initialized at glusterD init path. Since
socket file path of per node daemon demands the uuid of the node, MY_UUID macro
is invoked as part of the initialization.

The above flow breaks the usecases where a gluster image is built following a
template could be Dockerfile, Vagrantfile or any kind of virtualization
environment. This means bringing instances of this image would have same UUIDs
for the node resulting in peer probe failure.

Solution is to lazily initialize the services on demand.

Change-Id: If7caa533026c83e98c7c7678bded67085d0bbc1e
BUG: 1247012
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/11488
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Gaurav Kumar Garg 
Reviewed-by: Kaushal M 
Reviewed-on: http://review.gluster.org/11766

glusterd: Pass NULL in glusterd_svc_manager in glusterd_restart_bricks

2015-07-24T03:51:38+00:00

On restarting glusterd quota daemon is not started when  more than one
volumes are configured and quota is enabled only on 2nd volume.
This is because of while restarting glusterd it will restart all the bricks.
During brick restart it will start respective daemon by passing volinfo of
first volume. Passing volinfo to glusterd_svc_manager will imply daemon
managers will take action based on the same volume's configuration which
is incorrect for per node daemons.

Fix is to pass volinfo NULL while restarting bricks.

BUG: 1242882
Change-Id: Ie53fc452dc79811068a9397abca13c65de4a8359
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/11660
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee

glusterd: Fix failure in replace-brick when src-brick is offline

2015-07-14T18:39:39+00:00

Change-Id: I0fdb58e15da15c40c3fc9767f2fe4df0ea9d2350
BUG: 1242728
Reviewed-on: http://review.gluster.org/11651
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Signed-off-by: Anuradha Talur 
Reviewed-on: http://review.gluster.org/11656

tests: test cluster lock in heterogenious cluster

2015-06-24T10:57:50+00:00

Backport of http://review.gluster.org/11143

Change-Id: I421f50aeb89213d036b4b40f20a8e0d6bd78d60b
BUG: 1231608
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/11143
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Kaushal M 
Reviewed-on: http://review.gluster.org/11216
Reviewed-by: Krishnan Parthasarathi

tests: fix spurious failure in bug-857330/xml.t

2015-06-17T22:31:28+00:00

Backport of http://review.gluster.org/11054

get-task-status () used to always return 0 *until and unless* the CLI command
itself fails which is unlikely. However if the CLI command fails due to some
reason EXPECT_WITHIN will abort.

Change-Id: Ibe54dcdccc26b3ee003677fc3516cfed98b5c06f
BUG: 1232602
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/11054
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/11266
Reviewed-by: Vijay Bellur

glusterd: subvol_count value for replicate volume should be calculate correctly

2015-06-16T12:20:51+00:00

glusterd was crashing while trying to remove bricks from replica set
after shrinking nx3 replica to nx2 replica to nx1 replica.

This is because volinfo->subvol_count is calculating value from old
replica count value.

Change-Id: I1084a71e29c9cfa1cd85bdb4e82b943b1dc44372
BUG: 1231646
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/11165
Reviewed-by: Atin Mukherjee 
Reviewed-by: Ravishankar N 
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Krishnan Parthasarathi 
(cherry picked from commit 3fb18451311c34aeced1054472b6f81fc13dd679)
Reviewed-on: http://review.gluster.org/11224

dht: make lookup-unhashed=auto do something actually useful

2015-05-10T04:55:09+00:00

The key concept here is to determine whether a directory is "clean" by
comparing its last-known-good topology to the current one for the
volume.  These are stored as "commit hashes" on the directory and the
volume root respectively.  The volume's commit hash changes whenever a
brick is added or removed, and a fix-layout is done.  A directory's
commit hash changes only when a full rebalance (not just fix-layout)
is done on it.  If all bricks are present and have a directory
commit hash that matches the volume commit hash, then we can assume
that every file is in its "proper" place. Therefore, if we look for
a file in that proper place and don't find it, we can assume it's not
on any other subvolume and *safely* skip the global (broadcast to all)
lookup.

Change-Id: Id6ce4593ba1f7daffa74cfab591cb45960629ae3
BUG: 1220064
Reviewed-on-master: http://review.gluster.org/#/c/7702/
Signed-off-by: Jeff Darcy 
Signed-off-by: Shyam 
Reviewed-on: http://review.gluster.org/10729
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi 
Reviewed-by: Vijay Bellur

glusterd: remove replace brick with data migration support form cli/glusterd

2015-05-07T07:08:07+00:00

Replace-brick operation with data migration support have been
deprecated from gluster.

With this fix replace brick command will support only one commad

gluster volume replace-brick    {commit force}

Change-Id: Ib81d49e5d8e7eaa4ccb5830cfec2bc081191b43b
BUG: 1218602
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10577
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Kaushal M

tests: Check aux umount is unmounted for quota tests

2015-05-05T17:42:18+00:00

Change-Id: If57d08f3446755ea41f66ca258efcc8ea5a89063
BUG: 1218593
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/10480
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur 
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/10575

glusterd: initialize snapd svc at volume restore path

2015-04-28T08:53:35+00:00

In restore path snapd svc was not initialized because of which any glusterd
instance which went down and came back may have uninitialized snapd svc. The
reason I used 'may' is because depending on the nodes in the cluster. In a
single node cluster this wouldn't be a problem since glusterd_spawn_daemon takes
care of initializing it.

Backport of http://review.gluster.org/10304

Change-Id: I2da1e419a0506d3b2742c1cf39a3b9416eb3c305
BUG: 1215518
Signed-off-by: Atin Mukherjee 
Reviewed-on: http://review.gluster.org/10304
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Kaushal M 
(cherry picked from commit 18fd2fdd60839d737ab0ac64f33a444b54bdeee4)
Reviewed-on: http://review.gluster.org/10397
Reviewed-by: Krishnan Parthasarathi