Bug 1540660

Summary:	Introduce lock recovery options to prevent possible post-upgrade mount failures
Product:	[Community] GlusterFS	Reporter:	Shyamsundar <srangana>
Component:	protocol	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.0	CC:	amukherj, anoopcs, bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1540659	Environment:
Last Closed:	2018-06-20 18:26:46 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:	1540659
Bug Blocks:	1539842

Description Shyamsundar 2018-01-31 16:24:42 UTC

Patch being referred to in 4.0 would be: https://review.gluster.org/#/c/19392/

+++ This bug was initially created as a clone of Bug #1540659 +++

This patch: https://review.gluster.org/12363 removes the following options,
features.lock-heal
features.grace-timeout

Current worry is that if a volume has these options enabled, we would post-upgrading the server fail for client mounts (or even in other places). Also, removing these options post-upgrade may fail, as the options are not available, and hence may need editing the vol files.

We need to test and ensure that the above occurs, and if it does, we need to fix the situation in consultation with the glusterd team.

Current thoughts for fixing this up is to add these options back but as No-Ops, such that post upgrade functionality is removed, but the presence of the option itself does not cause failures.

Comment 1 Shyamsundar 2018-06-20 18:26:46 UTC

This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.