Bug 1579276

Summary: rpc: The gluster auth version is always AUTH_GLUSTERFS_v2
Product: [Community] GlusterFS Reporter: Kotresh HR <khiremat>
Component: rpcAssignee: Kotresh HR <khiremat>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1582063 (view as bug list) Environment:
Last Closed: 2018-10-23 15:09:12 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: 1582063    
Attachments:
Description Flags
Client logs
none
Brick logs none

Description Kotresh HR 2018-05-17 09:42:13 UTC 
Description of problem:
The new features like ctime which uses auth version - AUTH_GLUSTERFS_v3 is failing because the auth value is always AUTH_GLUSTERFS_v2

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

How reproducible:
Always happening in one machine and not reproducible in others

Steps to Reproduce:
1.  Create gluster volume, start it.
2.  Enable ctime and utime features on the volume
3.  Mount the volume
4.  Create a file, stat to record ctime
5.  chmod on file, stat to record ctime. 

Actual results:

The ctime is same between create and chmod.

Expected results:

The ctime should have changed between create and chmod

Additional info:
Comment 1 Worker Ant 2018-05-17 09:45:06 UTC 
REVIEW: https://review.gluster.org/20030 (rpc: Don't reset auth_value in disconnect) posted (#1) for review on master by Kotresh HR
Comment 2 Kotresh HR 2018-05-17 09:48:33 UTC 
Created attachment 1437868 [details]
Client logs

Client logs where AUTH_GLUSTERFS_v2 is being chosen over AUTH_GLUSTERFS_v3
Comment 3 Kotresh HR 2018-05-17 09:49:16 UTC 
Created attachment 1437869 [details]
Brick logs

Brick logs
Comment 4 Worker Ant 2018-05-24 05:26:43 UTC 
COMMIT: https://review.gluster.org/20030 committed in master by "Raghavendra G" <rgowdapp> with a commit message- rpc: Don't reset auth_value in disconnect

The auth_value was being reset to AUTH_GLUSTERFS_v2
during rpc disconnect. It shoud not be reset. The
disconnect during portmap request can race with
handshake. If handshake happens first and
disconnect later, auth_value would set to default
value and it never sets back to actual auth_value

fixes: bz#1579276
Change-Id: Ib46c9e01a97f6defb3fd1e0423fdb4b899b4a361
Signed-off-by: Kotresh HR <khiremat>
Comment 5 Worker Ant 2018-05-24 06:50:16 UTC 
REVISION POSTED: https://review.gluster.org/20076 (rpc: Don't reset auth_value in disconnect) posted (#2) for review on release-4.1 by Kotresh HR
Comment 6 Shyamsundar 2018-10-23 15:09:12 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-5.0, please open a new bug report.

glusterfs-5.0 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/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/