Description of problem: ----------------------- Gluster volumes created in a hybrid(mixed) cluster of RHS 2.1U2 & RHS 3.0, has snapshot related options shown up in 'gluster volume info' output Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHS 3.0 ( glusterfs-3.6.0.22-1.el6rhs ) How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Peer probe a Denali Node (RHS 3.0) from Corbett ( RHS 2.1 U2 ) (or) Create a cluster of 2 Nodes with RHS 2.1U2 and upgrade one node to RHS 3.0 2. Create a new volume ( of any type ) 3. Check 'gluster volume info' output Actual results: --------------- gluster volume snapshot related options are shown in 'gluster volume info' output Expected results: ----------------- op-version of the cluster is set to 2 ( since one of the node is in RHS 2.1U2), so snapshot related options should not be made available on the volume Additional info: ---------------- 1. 'gluster volume info' on RHS 3.0 shows the volume snapshot related options [root@rhss3 ~]# gluster v i Volume Name: dvol Type: Distribute Volume ID: 761e4c4c-76f3-4b37-af04-1e465a0a4139 Status: Started Snap Volume: no Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.70.37.136:/rhs/brick1/b1 Options Reconfigured: snap-max-hard-limit: 256 snap-max-soft-limit: 90 auto-delete: disable 2. 'gluster volume info' on RHS 2.1U2 doesn't have volume snapshot related options [root@corbett ~]# gluster v i Volume Name: dvol Type: Distribute Volume ID: 761e4c4c-76f3-4b37-af04-1e465a0a4139 Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.70.37.136:/rhs/brick1/b1
This is only relevant if we see it while upgrading from 2.1 to 3.0 not between 2 intermediate QE builds of 3.0.
With the patch http://review.gluster.org/#/c/8191/. snap-max-hard-limit, snap-max-soft-limit and auto-delete values will not be shown if they are not set explicitly. Currently we get below error message when one of the node in cluster is running glusterd version less than 3.6: root@rh1:~/workspace/git/glusterfs # gluster snapshot create snap1 vol1 snapshot create: failed: Another transaction is in progress Please try again after sometime. Snapshot command failed I will submit another patch to display correct error message when snapshot operation is performed on a cluster with op-version less than 3.6
Patch# http://review.gluster.org/#/c/8371/ posted upstream
Patch https://code.engineering.redhat.com/gerrit/#/c/29787/ submitted
During upgrade, from 2.1 to 3.0 in a mixed cluster, the cluster op-version will remain 2.1 till all the nodes are upgraded to 3.0. Hence in such a mixed cluster, gluster volume info will not show snap details. But if a cluster is having a cluster version 3.0, and volumes are already created in this cluster, upon attaching a node of version 2.1, although the cluster version will drop to 2.1, the volume files already generated will still have snap details. Hence in such a mixed cluster, gluster volume info will show snap details for the volumes already created.
Attaching node with version 2.1 to the node with version 3.0 can be done only if lower the op-version manually on the node with 3.0. I am not sure if we support creating a cluster by doing this.
[root@snapshot-03 glusterd]# rpm -qa | grep gluster glusterfs-fuse-3.6.0.27-1.el6rhs.x86_64 glusterfs-rdma-3.6.0.27-1.el6rhs.x86_64 glusterfs-libs-3.6.0.27-1.el6rhs.x86_64 glusterfs-api-3.6.0.27-1.el6rhs.x86_64 glusterfs-cli-3.6.0.27-1.el6rhs.x86_64 glusterfs-geo-replication-3.6.0.27-1.el6rhs.x86_64 glusterfs-debuginfo-3.6.0.27-1.el6rhs.x86_64 glusterfs-3.6.0.27-1.el6rhs.x86_64 glusterfs-server-3.6.0.27-1.el6rhs.x86_64 ----------------------------------------------------------------------- I have followed the below mentioned steps Step 1) Peer probed a fresh RHS 2.1 node to fresh RHS-3.0 node. Step 2) Made sure that operating-version is reduced to "2" in both the nodes. Step 3) Created a volume using bricks present in RHS-3.0 node. Step 4) Tried all snapshot commands from RHS-3.0 node. The error with which the commands fail is mentioned below: ------------------------------------------------ [root@snapshot-03 glusterd]# gluster snapshot create snap1 vol1 snapshot create: failed: Cluster operating version is lesser than the supported version for a snapshot Snapshot command failed [root@snapshot-03 glusterd]# gluster snapshot list Snapshot list : failed: Cluster operating version is lesser than the supported version for a snapshot Snapshot command failed [root@snapshot-03 glusterd]# gluster snapshot status Snapshot Status : failed: Cluster operating version is lesser than the supported version for a snapshot Snapshot command failed [root@snapshot-03 glusterd]# gluster snapshot delete snap1 Deleting snap will erase all the information about the snap. Do you still want to continue? (y/n) y snapshot delete: failed: Cluster operating version is lesser than the supported version for a snapshot Snapshot command failed ------------------------------------------------ In RHS-2.1 node the error is: [root@snapshot-07 glusterd]# gluster snapshot create snap1 vol1 unrecognized word: snapshot (position 0) The above error from RHS-2.1 node is as expected, because RHS 2.1 does not contain snapshot related information, and hence fail to recognize the word snapshot. ------------------------------------------------- I am moving this bug to VERIFIED state as the error displayed is correct.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1278.html