[Bugs] [Bug 1714973] New: upgrade after tier code removal results in peer rejection.

bugzilla at redhat.com bugzilla at redhat.com
Wed May 29 10:05:26 UTC 2019


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

            Bug ID: 1714973
           Summary: upgrade after tier code removal results in peer
                    rejection.
           Product: GlusterFS
           Version: mainline
            Status: NEW
         Component: glusterd
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: hgowtham at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:
the tier code was removed as a part of:
https://review.gluster.org/#/c/glusterfs/+/22664/

In this we failed to handle the is_tier_enabled.
This value is left in the info file for the older volumes.
So while upgrading the new gluster node didn't have this as it was removed and
the older one had it.
This ends in checksum mismatch and so the peer got rejected.

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

How reproducible:
100%

Steps to Reproduce:
1.create a node cluster without the tier code removal patch
2.update one node with the tier code removal patch
3.Once updated the nodes will get rejected.

Actual results:
The nodes are not supposed to be rejected.

Expected results:
The nodes get rejected.

Additional info:

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


More information about the Bugs mailing list