summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorsusant <spalai@redhat.com>2013-07-24 14:11:55 +0530
committerVijay Bellur <vbellur@redhat.com>2013-07-24 11:05:04 -0700
commite45e0037f6df6a0fab846a83fb2c99bb09417cf4 (patch)
treeb7c5dcae1b83eeab28792a50201a3e9437e6681e
parentaa04928a16858e70e6e87f2734e62b141de6f20e (diff)
cli :remove-brick process output leads to ambiguity
The output of remove-brick status as "Not started" leads to ambiguity.We should not show the status of the Server nodes which do not participate in the remove-brick process. Change-Id: I85fea40deb15f3e2dd5487d881f48c9aff7221de BUG: 986896 Signed-off-by: susant <spalai@redhat.com> Reviewed-on: http://review.gluster.org/5383 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vbellur@redhat.com>
-rw-r--r--cli/src/cli-rpc-ops.c9
1 files changed, 6 insertions, 3 deletions
diff --git a/cli/src/cli-rpc-ops.c b/cli/src/cli-rpc-ops.c
index fd58bf81d5c..28b92ee2fd2 100644
--- a/cli/src/cli-rpc-ops.c
+++ b/cli/src/cli-rpc-ops.c
@@ -1894,9 +1894,12 @@ xml_output:
}
size_str = gf_uint64_2human_readable(size);
- cli_out ("%40s %16"PRIu64 " %13s" " %13"PRIu64 " %13"PRIu64
- " %14s %16.2f", node_uuid, files, size_str, lookup,
- failures, status, elapsed);
+
+ if (strcmp (status, "not started")) {
+ cli_out ("%40s %16"PRIu64 " %13s" " %13"PRIu64 " %13"
+ PRIu64 " %14s %16.2f", node_uuid, files,
+ size_str, lookup, failures, status, elapsed);
+ }
GF_FREE(size_str);
i++;