Bug 1276423

Summary:	glusterd: probing a new node(>=3.6) from 3.5 cluster is moving the peer to rejected state
Product:	[Community] GlusterFS	Reporter:	Anand Nekkunti <anekkunt>
Component:	glusterd	Assignee:	Satish Mohan <smohan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, pkarampu, smohan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1276541 1276905 1277822 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:42:20 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:
Bug Depends On:
Bug Blocks:	1276541, 1276905, 1277822

Description Anand Nekkunti 2015-10-29 16:06:20 UTC

Description of problem:

probing a new  node(>=3.6)  from 3.5 cluster is moving the peer to rejected state 



How reproducible:
Always

Steps to Reproduce:
probe the 3.7 node from 3.5 cluster, then 3.7 node moves to rejected state due to check sum mismatch

Comment 1 Vijay Bellur 2015-10-29 16:24:27 UTC

REVIEW: http://review.gluster.org/12464 (glusterd: fixing vol info checksum mismatch) posted (#1) for review on master by Anand Nekkunti (anekkunt)

Comment 2 Vijay Bellur 2015-10-30 11:22:46 UTC

REVIEW: http://review.gluster.org/12464 (glusterd: fix info file checksum mismatch during upgrade) posted (#2) for review on master by Anand Nekkunti (anekkunt)

Comment 3 Vijay Bellur 2015-10-30 13:46:00 UTC

REVIEW: http://review.gluster.org/12464 (glusterd: fix info file checksum mismatch during upgrade) posted (#3) for review on master by Anand Nekkunti (anekkunt)

Comment 4 Vijay Bellur 2015-11-01 06:52:45 UTC

COMMIT: http://review.gluster.org/12464 committed in master by Kaushal M (kaushal) 
------
commit d29dd0747dbb2e7383867c97cbbaa8c41851db78
Author: anand <anekkunt>
Date:   Thu Oct 29 21:36:57 2015 +0530

    glusterd: fix info file checksum mismatch during upgrade
    
    issue: probing a new  node(>=3.6)  from 3.5 cluster is moving the peer to rejected state.
    
    fix: Disperse vol support is added from 3.6 release, so write disperse fields (disperse_count=0
    and redundancy_count=0) in vol info file  only if cluster version supported.
    
    Change-Id: I11d5e2e337b9bbaddc8e52ca7295ba481beb1132
    BUG: 1276423
    Signed-off-by: anand <anekkunt>
    Reviewed-on: http://review.gluster.org/12464
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaushal M <kaushal>
    Tested-by: NetBSD Build System <jenkins.org>

Comment 8 Niels de Vos 2016-06-16 13:42:20 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user