summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaushal M <kaushal@redhat.com>2013-05-21 13:01:08 +0530
committerVijay Bellur <vbellur@redhat.com>2013-05-21 04:29:57 -0700
commit8abe8f794913daa81d9f1dc0ddab26c9c414abf8 (patch)
tree8a4d561044183d76d1ca4b66c6fe877feb3b75ad
parent135a343605f3a015837cb44045a669d9ccf0dbd8 (diff)
tests: Modified test to use remove-brick instead of 'start' variant
Backport of change f75be77 from master 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. BUG: 878004 Change-Id: Ic6e1360ae5a5280d0d7efe8c3e9a0aa57dddb508 Signed-off-by: Kaushal M <kaushal@redhat.com> Reviewed-on: http://review.gluster.org/5052 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vbellur@redhat.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;