As RHS-3.0 is branched off from upstream, there are several op-version inconsistencies which could lead to improper behaviour with RHS-2.1. - RHS-3.0's op-version needs to be 3 instead of 4 as it is now. - Several checks done on op-version need to be changed to account for the first change. - Some of the options need their op-versions fixed as they differ between RHS-2.1 and RHS-3.0
Checked with glusterfs-3.6.0.22-1.el6rhs 1. Probed a new peer 2. Checked the contents of glusterd.info file [root@rhss1 glusterd]# cat glusterd.info UUID=2c1a999d-7ccd-4535-bf11-ce7799c62185 operating-version=30000 The second part of the test would be to check all options works well wrt to current change in op-version.
Created attachment 912701 [details] List of volume set options These are all the options which were tested for this bug
Tested with all the options that were introduced with op-version 30000 And the options that were supported with op-version as 2 Build - RHS 3.0 ( glusterfs-3.6.0.22-1.el6rhs ) Test steps : 1. Peer probed RHS 3.0 from RHS 2.1U2. op-version for cluster is set as 2 2. Tested all the new options introduced with op-version=30000 on RHS 3.0 All these commands were throwing error as expected. [root@rhss3 ~]# gluster volume set dvol diagnostics.client-log-flush-timeout 31 volume set: failed: Staging failed on 10.70.37.109. Error: Required op_version (30000) is not supported 3. Tested all the options with op-version as 2 These options are set and verified across the cluster List of options used for testing was attached as in comment4 Marking this bug as VERIFIED
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