Bug 1698471 - ctime feature breaks old client to connect to new server
Summary: ctime feature breaks old client to connect to new server
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1697907
Blocks: 1697820
TreeView+ depends on / blocked
 
Reported: 2019-04-10 12:38 UTC by Atin Mukherjee
Modified: 2019-04-22 13:33 UTC (History)
1 user (show)

Fixed In Version: glusterfs-6.1
Clone Of: 1697907
Environment:
Last Closed: 2019-04-17 15:22:13 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22544 0 None Merged glusterd: load ctime in the client graph only if it's not turned off 2019-04-16 10:50:58 UTC
Gluster.org Gerrit 22579 0 None Merged glusterd: fix loading ctime in client graph logic 2019-04-17 15:22:12 UTC

Description Atin Mukherjee 2019-04-10 12:38:15 UTC
+++ This bug was initially created as a clone of Bug #1697907 +++

Description of problem:

Considering ctime is a client side feature, we can't blindly load ctime xlator into the client graph if it's explicitly turned off, that'd result into backward compatibility issue where an old client can't mount a volume configured on a server which is having ctime feature.

Since ctime feature is enabled by default, any old client would still fail to connect to a new server until and unless this feature is turned off explicitly. Any client side feature when marked as enabled by default means there's a need to either turn of the feature if old client is to be made work with new servers or client needs to be upgraded to the latest version of server.

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

Server >= release-6, client <= release-5

How reproducible:
Always

Steps to Reproduce:
1. Create a volume on glusterfs-5 or higher
2. Mount the volume from a client which is running any version lower than glusterfs-5
3. Mount doesn't go through

Actual results:
Mount fails

Expected results:
Mount shouldn't fail



Additional info:

--- Additional comment from Worker Ant on 2019-04-09 09:48:09 UTC ---

REVIEW: https://review.gluster.org/22536 (glusterd: load ctime in the client graph only if it's not turned off) posted (#1) for review on master by Atin Mukherjee

--- Additional comment from Worker Ant on 2019-04-10 03:27:13 UTC ---

REVIEW: https://review.gluster.org/22536 (glusterd: load ctime in the client graph only if it's not turned off) merged (#1) on master by Atin Mukherjee

Comment 1 Worker Ant 2019-04-10 12:40:34 UTC
REVIEW: https://review.gluster.org/22544 (glusterd: load ctime in the client graph only if it's not turned off) posted (#1) for review on release-6 by Atin Mukherjee

Comment 2 Worker Ant 2019-04-16 10:50:59 UTC
REVIEW: https://review.gluster.org/22544 (glusterd: load ctime in the client graph only if it's not turned off) merged (#2) on release-6 by Shyamsundar Ranganathan

Comment 3 Worker Ant 2019-04-16 12:08:26 UTC
REVIEW: https://review.gluster.org/22579 (glusterd: fix loading ctime in client graph logic) posted (#1) for review on release-6 by Atin Mukherjee

Comment 4 Worker Ant 2019-04-17 15:22:13 UTC
REVIEW: https://review.gluster.org/22579 (glusterd: fix loading ctime in client graph logic) merged (#2) on release-6 by Shyamsundar Ranganathan

Comment 5 Shyamsundar 2019-04-22 13:33:13 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.1, please open a new bug report.

glusterfs-6.1 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2019-April/000124.html
[2] https://www.gluster.org/pipermail/gluster-users/


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