Bug 1417402

Summary:	automatic split resolution with size as policy should not work on a directory which is in metadata splitbrain
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nag Pavan Chilakam <nchilaka>
Component:	replicate	Assignee:	Sheetal Pamecha <spamecha>
Status:	CLOSED WONTFIX	QA Contact:	Nag Pavan Chilakam <nchilaka>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.2	CC:	amukherj, ksubrahm, ravishankar, rhs-bugs, spamecha, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1655050 (view as bug list)		Environment:
Last Closed:	2018-11-16 05:48:28 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:	1304593, 1655050

Description Nag Pavan Chilakam 2017-01-28 18:14:58 UTC

Description of problem:
=====================
when a directory is in metadata splitbrain,and split brain resolution is set to size, then we must not be automatically healing this file as there is no significant information to choose size as the option as the directories will be of same size

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

3.8.-4-13

How reproducible:
always

Steps to Reproduce:
1.create a x2 volume spanning on two nodes
2.mount on clients as below
c1 sees on n1
c2 only sees n2
c3 sees n1 and n2
3.now set fav child policy to size
4. create dir say dir1 from c3
5. disable self heal deamon
6. do a chmod of dir1 to say 0000 from c1
7. do a chmod of dir1 to say 0777 from c2
8. check heal info , must show dir1 as in splitbrain
9. now enable heal and trigger heal


Actual results:
=============
dir is getting resolved of splitbrain

Expected results:
==================
as size is the policy, split brain resolution must not work in this case as the size per-se is same. it should be splitbrain and let the admin takeup the stand on how to resolve it either through backend or manually thorugh cli

Additional info:

Comment 5 Atin Mukherjee 2018-11-11 21:58:15 UTC

This BZ hasn't received any updates since when it has reported. Are we going to work on this bug in coming months? Can we have a decision on this bug?