Bug 1540659

Summary:	Introduce lock recovery options to prevent possible post-upgrade mount failures
Product:	[Community] GlusterFS	Reporter:	Shyamsundar <srangana>
Component:	protocol	Assignee:	Anoop C S <anoopcs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	amukherj, 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:
Clones:	1540660 (view as bug list)		Environment:
Last Closed:	2019-11-18 06:42:58 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:	1540660

Description Shyamsundar 2018-01-31 16:23:41 UTC

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 Anoop C S 2019-11-18 06:42:58 UTC

We haven't had any complaints/issues for ~2 years around this volume options during upgrade. Moreover the dependent bug reported on v4.0 is no longer supported and was closed long back.

Thus closing this bug report on mainline version.