glusterfs.git/tests, branch v3.7.0beta1

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

Tests: fix spurious failures in trash.t

2015-04-26T08:54:30+00:00

Fix timing problems that cause rare spurious failures in trash.t

Backport of I673e033b53b6b4bb993c22fadbdcee725b2c1e96

BUG: 1212676
Change-Id: I319f94b7e099e189c08543da526d90d36318fe4b
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/10374
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Vijay Bellur

Tests: trash.t portability fixes

2015-04-26T04:51:25+00:00

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

Fix various portability problems in trash.t
- work around timing issues
- avoid wildcard usage only supported by bash

Original patch from Anoop C S and Jiffin Tony Thottan.

Removed LONGER_HEAL_TIMEOUT from previous patch as it
seems to run fine without it now.

BUG: 1212676
Change-Id: I0f6f484209ef4db7e0a7b733b863927cb248e73e
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/10346
Reviewed-by: Vijay Bellur

Tests: python portability

2015-04-23T05:31:11+00:00

Make sure to use $PYTHON defined from tests/env.rc so that we get the
path to the actually detected python interpreter.

Resubmit after rebase in hope that regression test will have less
spurious failures.

Backport of Ibf3e88f190d5e0c6a4a08e8d5ef9d0b5cba5078a

BUG: 1212676
Change-Id: I0c39d1c64423c8c9b99f8abf8f8cd813ed6a0deb
Signed-off-by: Emmanuel Dreyfus 
Reviewed-on: http://review.gluster.org/10287
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

Geo-rep: Adding regression tests for geo-rep

2015-04-13T10:01:49+00:00

This patch introduces upstream regression suit for geo-replication

    * Modifies cleanup (tests/include.rc) to remove everything but
      hook-scripts.

Prerequisites:
    * Passwordless SSH from root to root of current host.
    * Export /build/install/sbin and /build/install/bin to PATH
      variable for root user.

Change-Id: I433dd8bbb17edba9baaf516fe0dce3133ba39184
BUG: 1101111
Signed-off-by: Vijaykumar Koppad 
Signed-off-by: Ajeet Jha 
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/7392
Tested-by: Gluster Build System 
Reviewed-by: Aravinda VK 
Reviewed-by: Vijay Bellur

glusterd: Restarting glusterd should not reset bitrot tunable value to default

2015-04-13T08:46:56+00:00

Previously when user restart glusterd then bitrot tunable value for option
"scrub-throttle", "scrub-frequency", "scrub" cleared. glusterd was not storing
these bitrot tunable value properly.

With this fix it will store scrub-throttle, scrub-frequency, scrub, bitrot
tunable value in /var/lib/glusterd/vols//info file and it will resume
these value when glusterd restart.

Change-Id: I58e756e14fbb8513a6f878f808ea148e7aa33cb0
BUG: 1209751
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10159
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar

nfs: do not overwrite the return value and errno of resolve operation

2015-04-13T05:45:24+00:00

* In auth status check which is done in the resume function, the op_ret and
  op_errno values saved in nfs3_call_state are overwritten by the return value
  of the auth status check function.

Change-Id: Id4682ddd399c78a1cef6313a534892ef309c57a6
BUG: 1210338
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/10179
Tested-by: Gluster Build System 
Reviewed-by: Venky Shankar 
Reviewed-by: Niels de Vos

Tests: fix spurrious failure in mount-nfs-auth.t

2015-04-11T15:00:14+00:00

Work around a timing-caused spurious error introduced by
http://review.gluster.org/10047

BUG: 1129939
Change-Id: I0597377799f2464d9516fe710fa6e39c1f67a858
Signed-off-by: Emmanuel Dreyfus 
Signed-off-by: Jiffin Tony Thottan 
Reviewed-on: http://review.gluster.org/10182
Tested-by: Gluster Build System

cluster/ec: Fix readdir de-itransform

2015-04-11T09:11:15+00:00

Problem:
gf_deitransform returns the glbal client-id in the complete graph. So except
for the first disperse subvolume under dht, all the other disperse subvolumes
will return a client-id greater than ec->nodes, so readdir will always error
out in those subvolumes.

Fix:
Get the client subvolume whose client-id matches the client-id returned by
gf_deitransform of offset.

Change-Id: I26aa17504352d48d7ff14b390b62f49d7ab2d699
BUG: 1209113
Signed-off-by: Pranith Kumar K 
Reviewed-on: http://review.gluster.org/10165
Tested-by: Gluster Build System 
Reviewed-by: Xavier Hernandez

glusterd: bitd daemon should not start on the node which dont have any brick

2015-04-10T10:12:13+00:00

If user enable bitrot from node1 which have brick then glusterd starting
bitd daemon on node1 as well as glusterd starting bitd deamon on another node2
which does not have any brick (node1 and node2 are part of cluster).

With this fix glusterd will not start bitd daemon on the node which
don't have brick.

Change-Id: Ic1c68d204221d369d89d628487cdd5957964792e
BUG: 1207029
Signed-off-by: Gaurav Kumar Garg 
Reviewed-on: http://review.gluster.org/10071
Tested-by: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Venky Shankar 
Tested-by: Venky Shankar