Bug 1219845

Summary:	tiering: cksum mismach for tiered volume.
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	tiering	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.7.0	CC:	bugs, dlambrig
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	TIERING
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1215660	Environment:
Last Closed:	2015-05-14 17:29:40 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:	1215660
Bug Blocks:	1260923

Description Mohammed Rafi KC 2015-05-08 13:10:46 UTC

+++ This bug was initially created as a clone of Bug #1215660 +++

Description of problem:

If a tiered volume is created in a storage pool containing more than one node, then cksum in nodes will be different.

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

mainline

How reproducible:

always

Steps to Reproduce:
1.create a storage pool with two or more nodes
2.create a tiered volume
3.restart the glusterd
4.check peer status

Actual results:

peer will not be in a state "Peer in cluster"

Expected results:

peer should be in state "Peer in cluster"
Additional info:

--- Additional comment from Anand Avati on 2015-04-27 07:57:32 EDT ---

REVIEW: http://review.gluster.org/10406 (glusterd/tiering : cksum mismatch for tired volume) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-04-29 09:06:10 EDT ---

REVIEW: http://review.gluster.org/10406 (glusterd/tiering : cksum mismatch for tired volume) posted (#2) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-05-02 09:23:20 EDT ---

REVIEW: http://review.gluster.org/10406 (glusterd/tiering : cksum mismatch for tired volume) posted (#3) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-05-05 04:41:32 EDT ---

REVIEW: http://review.gluster.org/10406 (glusterd/tiering : cksum mismatch for tired volume) posted (#4) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Anand Avati on 2015-05-06 04:31:45 EDT ---

REVIEW: http://review.gluster.org/10406 (glusterd/tiering : cksum mismatch for tiered volume) posted (#6) for review on master by mohammed rafi  kc (rkavunga)

--- Additional comment from Mohammed Rafi KC on 2015-05-08 09:10:14 EDT ---

Fix is not merged in master, moving back to post state

Comment 1 Anand Avati 2015-05-09 11:47:21 UTC

REVIEW: http://review.gluster.org/10677 (glusterd/tiering : cksum mismatch for tiered volume) posted (#2) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 2 Anand Avati 2015-05-09 22:20:08 UTC

REVIEW: http://review.gluster.org/10677 (glusterd/tiering : cksum mismatch for tiered volume) posted (#3) for review on release-3.7 by Niels de Vos (ndevos)

Comment 3 Anand Avati 2015-05-10 14:07:07 UTC

REVIEW: http://review.gluster.org/10677 (glusterd/tiering : cksum mismatch for tiered volume) posted (#4) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 4 Anand Avati 2015-05-10 16:43:09 UTC

COMMIT: http://review.gluster.org/10677 committed in release-3.7 by Niels de Vos (ndevos) 
------
commit a492b22f5710f01ad3a18aad743d2b1eee058f6f
Author: Mohammed Rafi KC <rkavunga>
Date:   Mon Apr 27 17:18:36 2015 +0530

    glusterd/tiering : cksum mismatch for tiered volume
    
            Back port of http://review.gluster.org/#/c/10406
    
    Once we updated the volinfo from orginator node, the hot
    type was overwritten with volume type.
    
    Then the same dictionary was sent to peer node to perform
    the commit of attach-tier, that will cause hot type to
    replace with volume type, eventually end up in cksum
    mismatch
    
    Change-Id: I402dceb4d672d0b3a7b91a92f52c1057050dbedc
    BUG: 1219845
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: http://review.gluster.org/10677
    Reviewed-by: Niels de Vos <ndevos>
    Tested-by: NetBSD Build System
    Tested-by: Gluster Build System <jenkins.com>

Comment 5 Niels de Vos 2015-05-14 17:29:40 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:36:01 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 7 Niels de Vos 2015-05-14 17:38:23 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 8 Niels de Vos 2015-05-14 17:47:32 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user