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:
REVIEW: https://review.gluster.org/22785 (glusterd/tier: gluster upgrade broken because of tier) posted (#1) for review on master by hari gowtham
REVIEW: https://review.gluster.org/22785 (glusterd/tier: gluster upgrade broken because of tier) merged (#5) on master by Atin Mukherjee