Bug 1848893

Summary:	Spurious healing results in heal pending on the volume
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Sunil Kumar Acharya <sheggodu>
Component:	replicate	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	asakthiv, bmekala, ksubrahm, mwaykole, pprakash, puebele, ravishankar, rcyriac, rhs-bugs, rkothiya, sasundar, sheggodu, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.5.z Async Update	Flags:	puebele: needinfo+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-6.0-37.1	Doc Type:	Bug Fix
Doc Text:	Previously, entry heal was triggered just on the source bricks even when the sink brick was down.This led to the AFR pending-xattrs on the source bricks being reset unintentionally,resulting in gfid split-brains. With this update, entry heal is triggered only when all the bricks of the replica are up, thus preventing such spurious heals leading to gfid split-brains.	Story Points:	---
Clone Of:	1804164	Environment:	rhhiv
Last Closed:	2020-07-23 06:47:39 UTC	Type:	---
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:	1792821, 1804164

Comment 18 SATHEESARAN 2020-07-17 11:44:38 UTC

Verified with RHGS 3.5.2-async builds ( glusterfs-6.0-37.1 )

Validated with the following steps

1. Created the replica 3 volume
2. Used this volume as the storage domain in RHV
3. Created 10 VMs and started running kernel untar on these VMs
4. Kill of the brick and rebooted the host


When the host reboted, all the entries are healed and worked good

Comment 20 errata-xmlrpc 2020-07-23 06:47:39 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3122