From 4fa4b7f2c2b57d1055adb76e8258b0db176bc356 Mon Sep 17 00:00:00 2001 From: vmallika Date: Tue, 28 Oct 2014 12:25:43 +0530 Subject: glusterd/snapshot: Snapshot should be deactivated when it is created 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 --- tests/snapshot.rc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'tests/snapshot.rc') diff --git a/tests/snapshot.rc b/tests/snapshot.rc index 6ca276d194b..a0c92d96343 100755 --- a/tests/snapshot.rc +++ b/tests/snapshot.rc @@ -291,11 +291,15 @@ function snapshot_n_exists() { function snapshot_status() { local snap=$1; + local cli=$CLI_1; + if [ "$cli" = "" ]; then + cli=$CLI + fi #TODO: Right now just fetches the status of the single snap volume. #When snapshot will have multiple snap volumes, should have a #cummulative logic for status - $CLI_1 snapshot info $snap | grep "Status" | sed 's/.*: //'; + $cli snapshot info $snap | grep "Status" | sed 's/.*: //'; } -- cgit