summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKrishnan Parthasarathi <kparthas@redhat.com>2013-04-25 00:28:07 +0530
committerVijay Bellur <vbellur@redhat.com>2013-04-30 00:32:07 -0700
commitf75be775a9b191eb74f6cb4c161d9af36f2fdc97 (patch)
tree286b305e43d7abfb22e94c0416ea4722889bc660
parentee9984882e3b28e76fb3af5491a8d2bf22e432a3 (diff)
tests: Modified test to use remove-brick instead of 'start' variant
remove-brick start doesn't remove the brick from the volume immediately. It would wait until migration of data to other bricks are complete. Even when there is no data to be migrated, one can expect a finite delay from the time of remove-brick start command's exit and removal of brick(s). This may cause subsequent checks on brick count to fail in a non-deterministic manner. Also, renamed the test file name to reflect bug-id corresponding to community release. Change-Id: Ic43f011e251640decb68e46f4a10e0824ade0ac9 BUG: 878004 Signed-off-by: Krishnan Parthasarathi <kparthas@redhat.com> Reviewed-on: http://review.gluster.org/4885 Reviewed-by: Vijay Bellur <vbellur@redhat.com> Tested-by: Gluster Build System <jenkins@build.gluster.com>
-rw-r--r--tests/bugs/bug-878004.t (renamed from tests/bugs/bug-878873.t)3
1 files changed, 1 insertions, 2 deletions
diff --git a/tests/bugs/bug-878873.t b/tests/bugs/bug-878004.t
index efdcaca8925..5397be2a663 100644
--- a/tests/bugs/bug-878873.t
+++ b/tests/bugs/bug-878004.t
@@ -19,8 +19,7 @@ function brick_count()
TEST $CLI volume start $V0
-TEST $CLI volume remove-brick $V0 $H0:$B0/${V0}2 start;
-TEST $CLI volume remove-brick $V0 $H0:$B0/${V0}2 commit;
+TEST $CLI volume remove-brick $V0 $H0:$B0/${V0}2;
EXPECT '2' brick_count $V0
TEST $CLI volume remove-brick $V0 $H0:$B0/${V0}3;