Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1114415

Summary:	There is no way to monitor if the healing is successful when the brick is erased
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	replicate	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, ksubrahm, sia
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1117169 (view as bug list)		Environment:
Last Closed:	2017-08-23 06:33:11 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:
Bug Depends On:
Bug Blocks:	1117169

Description Pranith Kumar K 2014-06-30 03:27:24 UTC

Description of problem:

When "gluster volume heal <volname> full" is issued, there is no way to figure out if the healing is complete on the brick that is erased. This makes it very hard for users to confirm the self-heal is complete.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Pranith Kumar K 2015-08-27 13:30:16 UTC

With the new replace-brick implementation this bug is not applicable any more as '/' will be needing heal as soon as replace-brick is successful.

Comment 2 Karthik U S 2017-08-23 06:33:11 UTC

Closing the bug as per comment #1.