Bug 1714973

Summary:	upgrade after tier code removal results in peer rejection.
Product:	[Community] GlusterFS	Reporter:	hari gowtham <hgowtham>
Component:	glusterd	Assignee:	hari gowtham <hgowtham>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-03 13:32:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description hari gowtham 2019-05-29 10:05:26 UTC

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:

Comment 1 Worker Ant 2019-05-29 10:08:24 UTC

REVIEW: https://review.gluster.org/22785 (glusterd/tier: gluster upgrade broken because of tier) posted (#1) for review on master by hari gowtham

Comment 2 Worker Ant 2019-06-03 13:32:29 UTC

REVIEW: https://review.gluster.org/22785 (glusterd/tier: gluster upgrade broken because of tier) merged (#5) on master by Atin Mukherjee