[glusterd/snapshot] snapshot create force option

Implement force option in snapshot create i.e

1) Creation of snapshot fails if the original volume
bricks are down
2) With a force option creation of snapshot will continue
even if the original volume bricks are down.

This was the fix for bugs 1089527 and 1083502

Change-Id: I8de0242adf8ee0af00db9fa8701d86fabc12e7fc
BUG: 1090042
Signed-off-by: Joseph Fernandes <josferna@redhat.com>
Reviewed-on: http://review.gluster.org/7520
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>

1 files changed, 30 insertions, 0 deletions

diff --git a/tests/bugs/bug-1090042.t b/tests/bugs/bug-1090042.t
new file mode 100755
index 00000000000..364d8b2d66b
--- /dev/null
+++ b/tests/bugs/bug-1090042.t
@@ -0,0 +1,30 @@
+#!/bin/bash
+
+. $(dirname $0)/../include.rc
+. $(dirname $0)/../volume.rc
+. $(dirname $0)/../snapshot.rc
+
+cleanup;
+
+TEST init_n_bricks 3;
+TEST setup_lvm 3;
+TEST glusterd;
+
+TEST $CLI volume create $V0 replica 3 $H0:$L1 $H0:$L2 $H0:$L3;
+TEST $CLI volume start $V0;
+
+TEST kill_brick $V0 $H0 $L1;
+
+#Normal snap create should fail
+TEST !  $CLI snapshot create ${V0}_snap1 $V0;
+TEST !  snapshot_exists 0 ${V0}_snap1;
+
+#Force snap create should succeed
+TEST  $CLI snapshot create ${V0}_snap1 $V0 force;
+TEST  snapshot_exists 0 ${V0}_snap1;
+
+#Delete the created snap
+TEST  $CLI snapshot delete ${V0}_snap1;
+TEST  ! snapshot_exists 0 ${V0}_snap1;
+
+cleanup;