Bug 1168549

Summary:	Remove-brick: File permission (setuid) changes after migration of the file
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vivek Agarwal <vagarwal>
Component:	distribute	Assignee:	vsomyaju
Status:	CLOSED ERRATA	QA Contact:	Amit Chaurasia <achauras>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.1	CC:	achauras, mzywusko, nbalacha, nlevinki, nsathyan, psriniva, rcyriac, rhs-bugs, sankarshan, shmohan, spalai, ssamanta, storage-qa-internal, surs, vagarwal, vbellur, vsomyaju
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 2.1.6
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.71rhs-1.el6rhs	Doc Type:	Bug Fix
Doc Text:	Previously, if the setuid bit of a file was set and if the file was migrated after a remove-brick operation, the setuid bit did not exist after the file migration. With this fix, changes are made to ensure that the file permissions are retained with the setuid bit even after file migration.	Story Points:	---
Clone Of:	1061585	Environment:
Last Closed:	2015-01-28 10:43: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:	1061585
Bug Blocks:	1086228, 1162573, 1176659

Comment 4 Amit Chaurasia 2015-01-13 20:18:57 UTC

The suid are intact and as expected after the rebalance.

Though,in a corner case, I found that when the ownership of a file is attempted to change, the suid and sticky bit disappears. This happens without rebalance also hence not marking it this bug but will create a new bug for seprate follow-up of the issue.

Marking this bug verified.

Comment 5 Pavithra 2015-01-16 11:18:40 UTC

hi Susant,

Can you please review the edited doc text for technical accuracy and sign off?

Comment 6 Susant Kumar Palai 2015-01-16 12:16:49 UTC

Doc looks good.

Comment 8 errata-xmlrpc 2015-01-28 10:43:11 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://rhn.redhat.com/errata/RHBA-2015-0095.html