Bug 764566 (GLUSTER-2834) - Prevent heterogeneous GlusterFS versions between bricks
Summary: Prevent heterogeneous GlusterFS versions between bricks
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-2834
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-22 23:37 UTC by Vidya Sakar
Modified: 2015-11-03 23:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-24 06:46:18 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Vidya Sakar 2011-04-22 23:37:37 UTC
When a new volume is created and/or when a brick is added to an existing
volume, it should make sure that the GlusterFS version is the same in all the bricks. If this is not the case, it should throw a warning to the user.

Comment 1 Amar Tumballi 2011-09-27 05:49:54 UTC
Planing to keep 3.4.x branch as "internal enhancements" release without any features. So moving these bugs to 3.4.0 target milestone.

Comment 2 krishnan parthasarathi 2012-12-24 06:46:18 UTC
With the availability of op-version[1] feature, where all the storage nodes run 'compatible' versions of glusterfs binaries. It is not 'wrong' to have different bricks of a volume having different versions of glusterfs, as long as they are compatible. Closing this as not a bug. 


[1] - http://www.gluster.org/community/documentation/index.php/Features/Opversion


Note You need to log in before you can comment on or make changes to this bug.