[Bugs] [Bug 1684029] New: upgrade from 3.12, 4.1 and 5 to 6 broken

[bugzilla at redhat.com]

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

            Bug ID: 1684029
           Summary: upgrade from 3.12, 4.1 and 5 to 6 broken
           Product: GlusterFS
           Version: 6
            Status: NEW
        Whiteboard: gluster-test-day
         Component: core
          Severity: urgent
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: hgowtham at redhat.com
                CC: bugs at gluster.org
            Blocks: 1672818 (glusterfs-6.0)
  Target Milestone: ---
    Classification: Community



Description of problem:
While trying to upgrade from older versions like 3.12, 4.1 and 5 to gluster 6
RC, the upgrade ends in peer rejected on one node after other.

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


How reproducible:
100%

Steps to Reproduce:
1. create a replica 3 on older versions (3, 4, or 5)
2. kill the gluster process on one node and install gluster 6
3. start glusterd

Actual results:
the new version gets peer rejected. and the brick processes or not started by
glusterd.

Expected results:
peer reject should not happen. Cluster should be healthy.

Additional info:
Status shows the bricks on that particular node alone with N/A as status. Other
nodes aren't visible.
Looks like a volfile mismatch. 
The new volfile has "option transport.socket.ssl-enabled off" added while the
old volfile misses it.
The order of quick-read and open-behind are changed in the old and new
versions.

These changes cause the volfile mismatch and mess the cluster.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1672818
[Bug 1672818] GlusterFS 6.0 tracker
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.