glusterfs.git/tests/bugs/snapshot, branch v3.7.9

uss: validate USS option features.snapshot-directory

2016-02-15T08:20:39+00:00

This is a backport of http://review.gluster.org/#/c/9209

USS option features.snapshot-directory
   contains only 'alphanum, -, _, .'
   starts with dot (.)
   value cannot exceed 255 characters
and throws error for any other argument.

> Change-Id: Iad64635206ddf5599351020d99aafb3dd9d17bc1
> BUG: 1168819
> Signed-off-by: vmallika 
> Reviewed-on: http://review.gluster.org/9209
> Smoke: Gluster Build System 
> Reviewed-by: Avra Sengupta 
> Reviewed-by: Manikandan Selvaganesh 
> Reviewed-by: Rajesh Joseph 
> NetBSD-regression: NetBSD Build System 
> CentOS-regression: Gluster Build System 

Change-Id: I1b85d6851a223b51714c0498b457c41db99f5f58
BUG: 1305868
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/13409
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Rajesh Joseph

tests : Modifying crypt xlators unit tests

2016-02-09T14:12:49+00:00

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

The "encryption.master-key" should be set before enabling crypt xlators.
Otherwise glusterfs client process(like gluster-NFS) will crash due to the
failure in intialising crypt xlator.

You can see the following messages in client log file
[2016-01-14 08:13:15.740835] E [crypt.c:4298:master_set_master_vol_key]
0-test1-crypt: FATAL: missing master key
[2016-01-14 08:13:15.740859] E [MSGID: 101019]
[xlator.c:429lator_init] 0-test1-crypt: Initialization of volume
'test1-crypt' failed, review your volfile again
[2016-01-14 08:13:15.740890] E [MSGID: 101066]
[graph.c:324:glusterfs_graph_init] 0-test1-crypt: initializing
translator failed
[2016-01-14 08:13:15.740904] E [MSGID: 101176]
[graph.c:670:glusterfs_graph_activate] 0-graph: init failed
[2016-01-14 08:13:15.741676] W [glusterfsd.c:1231:cleanup_and_exit]
(-->/usr/sbin/glusterfs(mgmt_getspec_cbk+0x307) [0x40d287]
-->/usr/sbin/glusterfs(glusterfs_process_volfp+0x117) [0x4086c7]
-->/usr/sbin/glusterfs(cleanup_and_exit+0x4d) [0x407e1d] ) 0-: received
signum (0), shutting down

Upstream reference
-------------------
>Change-Id: I124deda505d128eacb15ca20fbdcd1593cb8eba3
>BUG: 1298520
>Signed-off-by: Jiffin Tony Thottan 
>Reviewed-on: http://review.gluster.org/13240
>Smoke: Gluster Build System 
>Reviewed-by: Niels de Vos 
>CentOS-regression: Gluster Build System 
>NetBSD-regression: NetBSD Build System 
>(cherry picked from commit ca4d4a26a553bac9c627bc6e6d6c9fa1f9435297)

Change-Id: I8073765b02cd4bebc202fbae5ef7558df25ea664
BUG: 1303033
Reviewed-on: http://review.gluster.org/13320
Smoke: Gluster Build System 
Reviewed-by: Jeff Darcy 
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

snapshot/clone : Fix tier pause failure for snapshot clone

2015-12-03T05:58:56+00:00

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

On a tiered volume, snapshot clone fails while trying to
pause tier, as we pass volname(snap) to the brick_op_phase module,
which tries to look for the snap volume amongst regular
volumes, and obviously doesn't find it and fail.

Well as snapshot volumes are read only volume, and will not
have tiering daemon acting upon them, there is really no need
to pause tiereing while taking clone of snapshot volumes. Hence
removing the code to pause and resume tiering during clone create.

Change-Id: I2266aba589a830a13a806c0d8a56fd8855143ccd
BUG: 1287538
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/12846
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Rajesh Joseph

snapshot: Inherit snap-max-hard-limit from original volume

2015-11-18T06:37:55+00:00

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

A snapshot should inherit snap-max-hard-limit from the original
volume while being created and when being restored to, it should
restore the same.

Similarly a clone taken from a snapshot should inherit
snap-max-hard-limit from the snapshot.

Change-Id: If8e90e2ffc10e22086b803ac8e2638a16bcec968
BUG: 1277390
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/12437
Tested-by: Gluster Build System 
Reviewed-by: mohammed rafi  kc 
Tested-by: NetBSD Build System 
Reviewed-by: Rajesh Joseph 
(cherry picked from commit 1f74a3efbd0337759878ffff5cd4ee6782ddfe3f)
Reviewed-on: http://review.gluster.org/12492

features/snap : cleanup the root loc in statfs

2015-10-20T08:39:38+00:00

Problem : In svc_statfs function, wipe_loc is getting called on loc
          passed by nfs. This loc is being used by svc_stat which
          throws erro if loc->inode is NULL.

Solution : wipe_loc should be called on local root_loc.
Back port of http://review.gluster.org/#/c/12123/

Change-Id: I9cc5ee3b1bd9f352f2362a6d997b7b09051c0f68
BUG: 1261732
Signed-off-by: Ashish Pandey 
Reviewed-on: http://review.gluster.org/12147
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Pranith Kumar Karampuri

snapshot: Fix snapshot info's xml output

2015-09-01T14:04:51+00:00

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

Display description field with (null) if
no description is present for the snapshot, instead
of removing the field altogether.

Change-Id: I965b08cd6e54eea56c32e2712fab7daa8a663f11
BUG: 1250388
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/11918
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Rajesh Joseph

snapshot: Fix terminating slash in brick mount path

2015-06-25T16:26:18+00:00

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

glusterd_find_brick_mount_path(), returns mount path,
with a terminating '/' at the ned of the string in
cases where the brick dir is a dir in the lvm root dir.

Ignoring the terminating '/' fixes the issue.

Change-Id: Ie7e63d37d48e2e03d541ae0076b8f143b8c9112f
BUG: 1232887
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/11294
Reviewed-by: Atin Mukherjee 
Tested-by: NetBSD Build System 
Reviewed-by: Rajesh Joseph

snapshot: Fix finding brick mount path logic

2015-06-09T14:20:06+00:00

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

Previously while finding brick mount paths
of snap volume's bricks, we were taking brick order
into consideration. This logic fails when a brick is
removed or a tier is added.

Hence modifying the logic to look for the first
occurence of the word "brick" in the brick path.
From there we iterate till we find a '/'. The string
till the first '/' after we encounter the word brick
is the brick mount path.

Change-Id: Ic85983c4e975e701cdfd4e13f8e276ac391a3e49
BUG: 1228592
Signed-off-by: Avra Sengupta 
(cherry picked from commit bf3a6dcdf3c8a8a64e7c864b56c4d9be60fca8e6)
Reviewed-on: http://review.gluster.org/11100
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Krishnan Parthasarathi

tests: Removing tests/bugs/snapshot/bug-1112559.t from test-suite

2015-05-21T08:45:05+00:00

     Backport Of Fix http://review.gluster.org/#/c/10840/

The fix that introduced this test has been reverted as part of design change.
Hence removing it from the test-suite

Change-Id: I7acaf387ec3035f736498a437c736fe70970d421
BUG: 1219782
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/10840
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Vijay Bellur 
(cherry picked from commit a61c788de737f81b9c21b176a26e21a078176ed9)
Reviewed-on: http://review.gluster.org/10871
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

snapshot/uss: fix regression failure in bug-1162498.t

2015-05-06T09:13:18+00:00

.snaps seems to take some time, before it is available based
on the state of the system. Using EXPECT_WITHIN instead of TEST
to check the contents of .snaps, hence giving it some time to
come up.

Change-Id: Iac166500d5a09ba8bab00d994c27a9ad0a01b9c3
BUG: 1218576
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/10518
Tested-by: Gluster Build System 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Pranith Kumar Karampuri 
Reviewed-on: http://review.gluster.org/10561