Bug 1540660 - Introduce lock recovery options to prevent possible post-upgrade mount failures
Summary: Introduce lock recovery options to prevent possible post-upgrade mount failures
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1540659
Blocks: glusterfs-4.0.0
TreeView+ depends on / blocked
 
Reported: 2018-01-31 16:24 UTC by Shyamsundar
Modified: 2018-06-20 18:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1540659
Environment:
Last Closed: 2018-06-20 18:26:46 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.