[Bugs] [Bug 1511903] New: 3.8 -> 3.12 rolling upgrade fails

[bugzilla at redhat.com]

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

            Bug ID: 1511903
           Summary: 3.8 -> 3.12 rolling upgrade fails
           Product: GlusterFS
           Version: 3.12
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: dchaplyg at redhat.com
                CC: bugs at gluster.org



Description of problem: Unable to upgrade gluster cluster to 3.12 version after
3.8 version


Version-Release number of selected component (if applicable): old one - 3.8,
new one - 3.12


How reproducible: Always


Steps to Reproduce:
1. Install 3 node gluster cluster using 3.8 version. I used binaries, shipped
with node-ng version 4.1.6-20170921
2. Upgrade one of those nodes to 3.12. I upgraded my node-ng to 4.2beta1 latest
tested 
3. Newly upgraded node will be rejected from a gluster cluster. 

Actual results: Node is rejected from cluster


Expected results: Node must be accepted


Additional info: Here is the log from the new node: 

[2017-11-09 05:15:08.481680] I [MSGID: 106163]
[glusterd-handshake.c:1271:__glusterd_mgmt_hndsk_versions_ack] 0-management:
using the op-version 30800
[2017-11-09 05:15:08.489219] I [MSGID: 106490]
[glusterd-handler.c:2608:__glusterd_handle_incoming_friend_req] 0-glusterd:
Received probe from uuid: 6b2193c1-63bd-408b-961e-51e01d
e486b7
[2017-11-09 05:15:11.165116] E [MSGID: 106010]
[glusterd-utils.c:2938:glusterd_compare_friend_volume] 0-management: Version of
Cksums data differ. local cksum = 1799370953, remote
 cksum = 3144964316 on peer 172.19.11.7
[2017-11-09 05:15:11.165328] I [MSGID: 106493]
[glusterd-handler.c:3852:glusterd_xfer_friend_add_resp] 0-glusterd: Responded
to 172.19.11.7 (0), ret: 0, op_ret: -1
[2017-11-09 05:15:11.175332] I [MSGID: 106493]
[glusterd-rpc-ops.c:476:__glusterd_friend_add_cbk] 0-glusterd: Received RJT
from uuid: 6b2193c1-63bd-408b-961e-51e01de486b7, host: 1

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.