From 1c430d2747f2c0960dcdcd9da4b253c89674bdd7 Mon Sep 17 00:00:00 2001 From: Venkatesh Somyajulu Date: Mon, 4 Feb 2013 13:51:16 +0530 Subject: glusterd: "volume heal info" doesn't report output properly Problem: "volume heal info" doesn't reports files to be healed when gluster* processes on one of the storage node is not running Change-Id: Iff7d41407014624e4da9b70d710039ac14b48291 BUG: 880898 Signed-off-by: Venkatesh Somyajulu Reviewed-on: http://review.gluster.org/4371 Tested-by: Gluster Build System Reviewed-by: Anand Avati --- tests/bugs/bug-880898.t | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 tests/bugs/bug-880898.t (limited to 'tests') diff --git a/tests/bugs/bug-880898.t b/tests/bugs/bug-880898.t new file mode 100644 index 00000000..a069d4a8 --- /dev/null +++ b/tests/bugs/bug-880898.t @@ -0,0 +1,23 @@ +#!/bin/bash + +. $(dirname $0)/../include.rc + +cleanup; + +TEST glusterd +TEST $CLI volume create $V0 replica 2 $H0:$B0/brick1 $H0:$B0/brick2 +TEST $CLI volume start $V0 +pkill glusterfs +uuid="" +for line in $(cat /var/lib/glusterd/glusterd.info) +do + if [[ $line == UUID* ]] + then + uuid=`echo $line | sed -r 's/^.{5}//'` + fi +done + +gluster volume heal $V0 info | grep "Status: self-heal-daemon is not running on $uuid"; +EXPECT "0" echo $? + +cleanup; -- cgit