andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

cli :remove-brick process output leads to ambiguity

Browse Source 
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>
This commit is contained in:
susant 2013-07-24 14:11:55 +05:30 committed by Vijay Bellur
parent aa04928a16
commit e45e0037f6
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
cli/src/cli-rpc-ops.c
View File

@ -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++;