Bug 1314646

Summary:	Incorrect error message on CLI on launching heal
Product:	[Community] GlusterFS	Reporter:	Anuradha <atalur>
Component:	replicate	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, ravishankar, smohan
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-02 05:18:26 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 Anuradha 2016-03-04 07:16:04 UTC

Description of problem:
When self-heal-daemon is off, and 'gluster volume heal <volname>' is run, the following error is displayed :

Launching heal operation to perform index self heal on volume test has been unsuccessful on bricks that are down. Please check if all brick processes are running.

This is incorrect.
Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. create a replicate volume
2. disable self-heal-daemon
3. try to launch heal using the above mentioned command

Actual results:
Errors out with the following message :
Launching heal operation to perform index self heal on volume test has been unsuccessful on bricks that are down. Please check if all brick processes are running.

Expected results:
Error message should be :
Self-heal-daemon is disabled. Heal will not be triggered on volume test

Additional info:

Comment 2 Ravishankar N 2017-03-02 05:18:26 UTC


*** This bug has been marked as a duplicate of bug 1388509 ***