Description of problem:
rebalance status is  ambiguous In case of Failures,
e.g.
1)
[root@OVM2 ~]# gluster volume rebalance dht1 status
                                    Node Rebalanced-files          size       scanned      failures       skipped               status   run time in secs
                               ---------      -----------   -----------   -----------   -----------   -----------         ------------     --------------
                               localhost            55722         1.1GB        197894            29             1            completed            5177.00
                            10.70.35.228            52862       988.4MB        172572            27             3            completed            5084.00
                            10.70.35.212              308        51.3MB       3543049             0             0            completed           25631.00
volume rebalance: dht1: success: 


even though failure column has xx count, status says 'completed'.

2) as mentioned in bug 1064481 rebalance process hasn't completed crawl but status shows completed

Version-Release number of selected component (if applicable):
3.4.0.59rhs-1.el6rhs.x86_64

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
need clarification on rebalance status:-
- In which Cases 'status' column should show 'failed' or 'completed'
- 'failures' column should show count of file migration failures only or should include Directory layout fixing failures also.



Additional info: