Bug 1550315

Summary:	[GSS] ACL settings on directories is different on newly added bricks compared to original bricks after rebalance completion
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Prashant Dhange <pdhange>
Component:	distribute	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Prasad Desala <tdesala>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	rhgs-3.3	CC:	amukherj, knakai, moagrawa, nbalacha, pdhange, pkarampu, rhinduja, rhs-bugs, rtalur, sheggodu, srmukher, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.4.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	dht-perms
Fixed In Version:	glusterfs-3.12.2-8	Doc Type:	If docs needed, set a value
Doc Text:	Earlier for a distributed volume, custom extended attribute value for a directory did not show the correct value after stop/start or even the newly added brick.dht was not able to sync xattr value because it was difficult to figure out the source of truth. With this fix, a new MDS volume similar to hashed subvol is introduced which will be considered as a source of truth at the time of updating custom xattrs for the directory.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 06:42:45 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:	1503138, 1550771

Comment 38 Prasad Desala 2018-08-22 13:24:26 UTC

Verified this BZ on glusterfs version: 3.12.2-16.el7rhgs.x86_64.

Ran below polarion cases and didn't see any inconsistencies.

RHG3-13145
Directory: sub-volume down - custom extended attribute validation getfattr, setfattr

RHG3-13111 Metadata ops on directory: sub-volume down

Moving this BZ to Verified state.

Comment 39 Srijita Mukherjee 2018-09-03 15:39:25 UTC

Updated the doc text. Kindly review

Comment 41 errata-xmlrpc 2018-09-04 06:42:45 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/RHSA-2018:2607