Bug 1004685 - Volume cksums differ after one of the nodes in a 2.0 cluster is upgraded to 2.1.
Summary: Volume cksums differ after one of the nodes in a 2.0 cluster is upgraded to 2.1.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: 2.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Krutika Dhananjay
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-05 08:41 UTC by Krutika Dhananjay
Modified: 2015-08-10 07:44 UTC (History)
4 users (show)

Fixed In Version: glusterfs-v3.4.0.33rhs
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-10 07:44:21 UTC
Embargoed:

Attachments (Terms of Use)

Description Krutika Dhananjay 2013-09-05 08:41:42 UTC 
Description of problem:
After upgrading one of the nodes of a 2.0-all cluster to 2.1, the peer gets rejected with volume checksum mismatch.

Version-Release number of selected component (if applicable):
RHS-2.1 built from source.

How reproducible:


Steps to Reproduce:

1. Create a cluster of 2 nodes, both operating in version 2.0.
2. Create a volume with bricks on both the nodes.
3. Start the volume.
4. Mount the volume from a 2.0 client.
5. Upgrade one of the servers to 2.1.
6. Restart glusterd on this 2.1 node.
7. The node gets rejected with volume cksum mismatch.

Actual results:
Volume cksum computed on the two nodes differ.

Expected results:
Volume cksum must be the same on both the nodes.

Additional info:
Comment 4 Krutika Dhananjay 2013-09-19 11:25:49 UTC 
The fix is available in glusterfs-v3.4.0.33rhs, hence moving the state of the bug to ON_QA.
Comment 5 Sachidananda Urs 2013-12-16 05:43:39 UTC 
This is a sanity only bug.
Ref: https://mojo.redhat.com/docs/DOC-20570 - Upgrade tests.
Note You need to log in before you can comment on or make changes to this bug.