Bug 1564027

Summary:	disabling gfid2path on rhgs-3.4.0 requires brick restart
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Ravishankar N <ravishankar>
Component:	posix	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED WONTFIX	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	amukherj, atumball, khiremat, nchilaka, rhs-bugs, storage-qa-internal
Target Milestone:	---	Keywords:	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:		Environment:
Last Closed:	2018-11-20 03:27:09 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:

Description Ravishankar N 2018-04-05 07:07:13 UTC

Description of problem:
If gfid2path is disabled on a volume that was upgraded from rhgs-3.3.1 to rhgs-3.40, it still goes ahead and creates the xattr.

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

How reproducible:
Always

Steps to Reproduce:
1. Created a single node, replica 3 volume and mounted on the same node using rhgs.3.2.0
2. Upgraded the cluster op-version to 31301
3. Created a file from mount; gfid2path xattr is set as expected. (since the feature is on by default).
4. Disable gfid2path: gluster v set <volname> gfid2path disable
5. Create a new file from the mount. The file still has the xattr set.

Note:
Once the brick processes are restarted, the attr is no longer created. So if disabling gfid2path requires a brick restart and this is not a bug, we need to have this documented.

Comment 3 Atin Mukherjee 2018-04-07 09:59:19 UTC

There's a proposal to disable gfid2patch in downstream. if that's the case, this bug will be invalidated. So should we go ahead and disable gfid2path in 3.4.0?

Comment 8 Amar Tumballi 2018-11-20 03:27:09 UTC

We want this xattr to be present in RHGS3.4+ versions, and there is no way for users to fix this. Hence closing this as WONTFIX. Also, for now, many brick options are like this, where if they are set, to get into effect, it needs to be restarted.