+++ This bug was initially created as a clone of Bug #1091986 +++ Description of problem: Both the snapshot feature and persistent AFR xattrs implementation will work only if op-version >=4. To that effect we would need a gluster CLI command to bump up the glusterd op-version when an existing cluster is upgraded to the release containing these features. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Form a cluster and create a volume with a glusterfs release having cluster op-version less than 4. 2. Upgrade all nodes to the release having snapshot/ persistent AFR xattrs features. 3. Try snapshot/ add-brick/ remove-brick operations Actual results: Add/remove brick operations fail with the message: One or more nodes do not support the required op-version. Cluster op-version must atleast be 4. Similarly snapshots would also fail with an appropriate message (not checked the exact message yet). Expected results: These features should work.
REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#1) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#2) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#3) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#4) for review on master by Kaushal M (kaushal)
REVIEW: http://review.gluster.org/7603 (glusterd: Allow bumping up the cluster op-version) posted (#5) for review on master by Kaushal M (kaushal)
COMMIT: http://review.gluster.org/7603 committed in master by Krishnan Parthasarathi (kparthas) ------ commit fb173e9a10d62d49cc8b57c6b3c5bbdf1b326c18 Author: Kaushal M <kaushal> Date: Tue Apr 29 19:12:20 2014 +0530 glusterd: Allow bumping up the cluster op-version This patch allows a user to bump up the cluster op-version by doing # gluster volume set all cluster.op-version <OP-VERSION> The op-version will be bumped only if - all the peers in the cluster support it, and - the new op-version is greater than the current cluster op-version This set operation will not do any other change other than changing and saving the cluster op-version in the glusterd.info file. It will NOT, - change any existing volume - add the option to the global options list - fix the cluster op-version to the given version, it can be bumped up by other volume set commands. Change-Id: I084b4fcc45e79dc2ca7b7680d7bb371bb175af39 BUG: 1092592 Signed-off-by: Kaushal M <kaushal> Reviewed-on: http://review.gluster.org/7603 Reviewed-by: Atin Mukherjee <amukherj> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: Krishnan Parthasarathi <kparthas>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
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.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users