REVIEW: https://review.gluster.org/18487 (cli/afr: gluster volume heal info "healed" command output is not appropriate) posted (#1) for review on release-3.12 by MOHIT AGRAWAL (email@example.com)
COMMIT: https://review.gluster.org/18487 committed in release-3.12 by jiffin tony Thottan (firstname.lastname@example.org)
Author: Mohit Agrawal <email@example.com>
Date: Tue Oct 25 19:57:02 2016 +0530
cli/afr: gluster volume heal info "healed" command output is not appropriate
Problem: "gluster volume heal info [healed] [heal-failed]" command
output on terminal is not appropriate in case of down any volume.
Solution: To make message more appropriate change the condition
in function "gd_syncop_mgmt_brick_op".
Test : To verify the fix followed below procedure
1) Create 2*3 distribute replicate volume
2) set self-heal daemon off
3) kill two bricks (3, 6)
4) create some file on mount point
5) bring brick 3,6 up
6) kill other two brick (2 and 4)
7) make self heal daemon on
8) run "gluster v heal <vol-name>"
Note: After apply the patch options (healed | heal-failed) will deprecate
from command line.
> BUG: 1388509
> Change-Id: I229c320c9caeb2525c76b78b44a53a64b088545a
> Signed-off-by: Mohit Agrawal <firstname.lastname@example.org>
> (Cherry pick from commit d1f15cdeb609a1b720a04a502f7a63b2d3922f41)
Signed-off-by: Mohit Agrawal <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-glusterfs-3.12.2, please open a new bug report.
glusterfs-glusterfs-3.12.2 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.
*** Bug 1500658 has been marked as a duplicate of this bug. ***
*** Bug 1500660 has been marked as a duplicate of this bug. ***