[Bugs] [Bug 1544699] New: Rolling upgrade to 4.0 is broken

[bugzilla at redhat.com]

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

            Bug ID: 1544699
           Summary: Rolling upgrade to 4.0 is broken
           Product: GlusterFS
           Version: mainline
         Component: protocol
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: anoopcs at redhat.com
                CC: anoopcs at redhat.com, bugs at gluster.org,
                    pkarampu at redhat.com, ravishankar at redhat.com,
                    srangana at redhat.com
        Depends On: 1544366



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

Description of problem:
Was trying to test https://review.gluster.org/#/c/19538/ when I found that
rolling upgrade from glusterfs-3.13 to the yet to be released glusterfs 4.0 is
broken.  In a  2 node setup, when one node is upgraded, clients mounted on each
node can only see the local bricks and not the ones on the other node. I see
the following errors in the client logs.:

E [MSGID: 114044] [client-handshake.c:1093:client_setvolume_cbk]
0-testvol-client-1: SETVOLUME on remote-host failed: lock state version not
supplied [Invalid argument]


Steps to Reproduce:
1. Create a 2 node 1x2 volume and mount locally on each node, all on
glustefs-3.13.
2. Upgrade one of the nodes to 4.0 branch
3. Clients can see only local bricks.

--- Additional comment from Anoop C S on 2018-02-12 17:12:17 IST ---

I think I failed to handle the scenario where clients are upgraded before
servers.

RCA:(new clients[>=4.0] and old servers[<=3.13])
SETVOLUME request from client post-upgrade does not contain its lk-version in
dictionary that is being passed onto
server(https://review.gluster.org/#/c/12363/). This means that the server side
check for "clnt-lk-version" inside the received dictionary would fail and error
is returned back to new client.

--- Additional comment from Ravishankar N on 2018-02-12 19:37:17 IST ---

(In reply to Anoop C S from comment #1)
> I think I failed to handle the scenario where clients are upgraded before
> servers.
> 
FWIW, it is not just the mount but things like self-heal-daemon and glfsheal
(gfapi based program that is used to display 'heal info') were also affected.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1544366
[Bug 1544366] Rolling upgrade to 4.0 is broken
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.