[Bugs] [Bug 1582063] New: rpc: The gluster auth version is always AUTH_GLUSTERFS_v2

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1582063

            Bug ID: 1582063
           Summary: rpc: The gluster auth version is always
                    AUTH_GLUSTERFS_v2
           Product: GlusterFS
           Version: 4.1
         Component: rpc
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: bugs at gluster.org
        Depends On: 1579276



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

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:

--- Additional comment from Worker Ant on 2018-05-17 05:45:06 EDT ---

REVIEW: https://review.gluster.org/20030 (rpc: Don't reset auth_value in
disconnect) posted (#1) for review on master by Kotresh HR

--- Additional comment from Kotresh HR on 2018-05-17 05:48 EDT ---

Client logs where AUTH_GLUSTERFS_v2 is being chosen over AUTH_GLUSTERFS_v3

--- Additional comment from Kotresh HR on 2018-05-17 05:49 EDT ---

Brick logs

--- Additional comment from Worker Ant on 2018-05-24 01:26:43 EDT ---

COMMIT: https://review.gluster.org/20030 committed in master by "Raghavendra G"
<rgowdapp at redhat.com> 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 at redhat.com>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1579276
[Bug 1579276] rpc: The gluster auth version is always AUTH_GLUSTERFS_v2
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.