From bdbd092e2caf79a2cfd6cda507af624e9861ae30 Mon Sep 17 00:00:00 2001 From: Sakshi Date: Thu, 28 May 2015 10:49:36 +0530 Subject: glusterd : check if all bricks are started before performing remove-brick Change-Id: Ie9e24e037b7a39b239a7badb983504963d664324 BUG: 1225716 Signed-off-by: Sakshi Reviewed-on: http://review.gluster.org/10954 Tested-by: NetBSD Build System Tested-by: Gluster Build System Reviewed-by: Atin Mukherjee --- tests/bugs/glusterd/bug-857330/xml.t | 2 ++ 1 file changed, 2 insertions(+) (limited to 'tests/bugs/glusterd/bug-857330/xml.t') diff --git a/tests/bugs/glusterd/bug-857330/xml.t b/tests/bugs/glusterd/bug-857330/xml.t index c25a8a63251..6b87f21d9c1 100755 --- a/tests/bugs/glusterd/bug-857330/xml.t +++ b/tests/bugs/glusterd/bug-857330/xml.t @@ -52,6 +52,8 @@ TEST $CLI volume replace-brick $V0 $H0:$B0/${V0}2 $H0:$B0/${V0}3 commit force ################## ## Remove-brick ## ################## +EXPECT_WITHIN $PROCESS_UP_TIMEOUT "Y" brick_up_status $V0 $H0 $B0/${V0}3 + COMMAND="volume remove-brick $V0 $H0:$B0/${V0}3 start" PATTERN="task-id" TEST check-and-store-task-id-xml -- cgit