Bug 1277823

Summary:	[upgrade] After upgrade from 3.5 to 3.6, probing a new 3.6 node is moving the peer to rejected state
Product:	[Community] GlusterFS	Reporter:	Anand Nekkunti <anekkunt>
Component:	glusterd	Assignee:	Anand Nekkunti <anekkunt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	amukherj, bugs, gluster-bugs, nlevinki, nsathyan, pprakash, rcyriac, rhs-bugs, sasundar, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	glusterd
Fixed In Version:	glusterfs-3.6.7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1262805	Environment:
Last Closed:	2015-12-02 08:25:37 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:	1248895, 1262793, 1262805
Bug Blocks:	1267567

Comment 1 Anand Nekkunti 2015-11-04 07:21:03 UTC

patch: http://review.gluster.org/#/c/12500/1

Comment 2 Vijay Bellur 2015-11-18 12:43:56 UTC

COMMIT: http://review.gluster.org/12500 committed in release-3.6 by Raghavendra Bhat (raghavendra) 
------
commit 89962044417e1d01a31dee72357d5ebcae0f44cb
Author: Atin Mukherjee <amukherj>
Date:   Mon Sep 14 17:09:29 2015 +0530

    glusterd: call glusterd_store_volinfo in bump up op-version
    
    After an upgrade, op-version is expected to be updated through gluster volume
    set. If the new version introduces any feature which changes volinfo structure
    without storing the default values of these new options would result into cksum
    issues.
    
    Backport of:
    >Change-Id: I57b4667f3403839811735bf66bef29e5200a9241
    >BUG: 1262805
    >Signed-off-by: Atin Mukherjee <amukherj>
    >Reviewed-on: http://review.gluster.org/12171
    >Tested-by: Gluster Build System <jenkins.com>
    >Reviewed-by: Krishnan Parthasarathi <kparthas>
    >Reviewed-by: Gaurav Kumar Garg <ggarg>
    >(cherry picked from commit c3ed484af54e32c1ef2300cda652604d75dc9d20)
    
    Change-Id: I0c8d3cc7722b4a04e129c01792b80e27a7e8e59f
    BUG: 1277823
    Reviewed-on: http://review.gluster.org/12500
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Raghavendra Bhat <raghavendra>

Comment 3 Raghavendra Bhat 2015-12-02 08:25:37 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.6.7, please open a new bug report.

glusterfs-3.6.7 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://www.gluster.org/pipermail/gluster-devel/2015-December/047260.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user