Bug 826406

Summary:	[glusterfs-3.3.0q43]: wrong message for heal info command
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	cli	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	pre-release	CC:	gluster-bugs, sdharane
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:19:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joe Julian 2012-05-30 06:57:38 UTC

Calling "gluster volume heal vmimages info" results in the message, "Heal operation on volume vmimages has been successful" which I imagine is referring to the rpc call, but implies that healing has been successful. Which is misleading.

Comment 1 Pranith Kumar K 2012-06-14 02:08:54 UTC

Joe Julian,
     Here are the new outputs:
[root@pranithk-laptop r2]# gluster volume heal r2 info
Gathering Heal info on volume r2 has been successful

Brick pranithk-laptop:/gfs/r2_0
Number of entries: 0
Status: Brick is Not connected

Brick pranithk-laptop:/gfs/r2_1
Number of entries: 11
/
/9
/10
/3
/4
/1
/6
/2
/7
/5
/8

[root@pranithk-laptop r2]# gluster volume heal r2 
Launching Heal operation on volume r2 has been successful
Use heal info commands to check status
[root@pranithk-laptop r2]# 

Let me know if you have more suggestions.

Comment 2 Joe Julian 2012-06-15 05:37:38 UTC

Looks good to me.