glusterfs.git/tests/snapshot.rc, branch v3.7.18

tests: Backport all changes to tests dir

2016-05-04T18:47:11+00:00

Test framework should be the same on all the branches. This is a copy
of all the files under tests dir from master branch. New tests in
master have not been backported, but changes to existing tests have
been.

Change-Id: I75747c525aabbd9247473dd29b3a0e7a7d93c827
BUG: 1316533
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/13683
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster 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

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: Handshake with glusterd is not proper

2015-05-08T09:26:35+00:00

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

If a snap is activated or deactivated, when a node is down,
it is not retrieving the data properly during the handshake
of glusterd

With this patch, a version check will made when a glusterd
is started running. If there is a mismach in version, then
peers will exchange the healed data.

Change-Id: I8bd2a347723db2194d3fa73295878b4dd2e9be5d
BUG: 1219744
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/9664
Tested-by: Gluster Build System 
Reviewed-by: Avra Sengupta 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Kaushal M 
Reviewed-on: http://review.gluster.org/10661

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

tests: fix volume_exists to be used from EXPECT_WITHIN

2015-04-01T08:49:37+00:00

Fixes the spurious volume-snapshot-clone.t regression failures.  In
brief, the problem is that the script wasn't waiting for config commands
to complete, and would *sometimes* query the status of a volume while
that volume was still being deleted.

It turns out that "!" doesn't work properly from EXPECT_WITHIN, so there
was a choice between changing that or changing volume_exists.  This
seemed less risky.  Because of code duplication, two instances of the
function had to be changed, and the other caller (volume-snapshot.t) did
too.

Change-Id: I766d4dc7c5b11038ede8e45d9d1f29cd02a622a0
BUG: 1163543
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/10053
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Vijay Bellur

snapshot: append timestamp with snapname

2015-03-10T11:42:00+00:00

Appending GMT time stamp with snapname by default.
If no-timestamp flag is given during snapshot creation,
then time stamp will not append with snapname;

Initial consumer of this feature is Samba's Shadow Copy
feature. This feature allows Windows user to get previous 
revisions of a file. For this feature to work snapshot 
names under .snaps folder (USS) should have timestamp in 
following format appended:
@GMT-YYYY.MM.DD-hh.mm.ss

PS: https://www.samba.org/samba/docs/man/manpages/vfs_shadow_copy2.8.html

This format is configurable by Samba conf file. Due to a 
limitation in Windows directory access the exact format 
cannot be used by USS. Therefore we have modified the file 
format to:
_GMT-YYYY.MM.DD-hh.mm.ss

Snapshot scheduling feature also required to append timestamp 
to the snapshot name therefore timestamp is appended in 
snapshot creation itself instead of doing the changes in 
snapview server.

More info:
https://www.mail-archive.com/gluster-users@gluster.org/msg18895.html

Change-Id: Idac24670948cf4c0fbe916ea6690e49cbc832d07
BUG: 1189473
Signed-off-by: Mohammed Rafi KC 
Reviewed-on: http://review.gluster.org/9597
Tested-by: Gluster Build System 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

tests: move all test-cases into component subdirectories

2015-01-06T11:24:24+00:00

There are around 300 regression tests, 250 being in tests/bugs. Running
partial set of tests/bugs is not easy because this is a flat directory
with almost all tests inside.

It would be valuable to make partial test/bugs easier, and allow the use
of mulitple build hosts for a single commit, each running a subset of
the tests for a quicker result.

Additional changes made:
- correct the include path for *.rc shell libraries and *.py utils
- make the testcases pass checkpatch
- arequal-checksum in afr/self-heal.t was never executed, now it is
- include.rc now complains loudly if it fails to find env.rc

Change-Id: I26ffd067e9853d3be1fd63b2f37d8aa0fd1b4fea
BUG: 1178685
Reported-by: Emmanuel Dreyfus 
Reported-by: Atin Mukherjee 
URL: http://www.gluster.org/pipermail/gluster-devel/2014-December/043414.html
Signed-off-by: Niels de Vos 
Reviewed-on: http://review.gluster.org/9353
Reviewed-by: Kaleb KEITHLEY 
Reviewed-by: Emmanuel Dreyfus 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd/snapshot: Snapshot should be deactivated when it is created

2014-11-12T12:36:11+00:00

By default snapshot should be deactivated and this should be a
configurable option.

This behaviour can be configured by the command below:
gluster snapshot config activate-on-create 

Change-Id: I1911595c32beed43bb2fca4bf99f0d264b422513
BUG: 1157991
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/8985
Tested-by: Gluster Build System 
Reviewed-by: Avra Sengupta 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Kaushal M