Features on the 3.8 roadmap should have the GD_OP_VERSION_3_8_0 set. Features that are not scheduled for inclusion in 3.8 should stick with GD_OP_VERSION_4_0_0. https://www.gluster.org/community/roadmap/3.8/
REVIEW: http://review.gluster.org/14551 (glusterd: set the maximum op-version for 3.8.0) posted (#1) for review on release-3.8 by Niels de Vos (ndevos)
COMMIT: http://review.gluster.org/14551 committed in release-3.8 by Niels de Vos (ndevos) ------ commit a7180391e12c8f0549ce573dbaef55f3cbd1060a Author: Niels de Vos <ndevos> Date: Fri May 27 18:39:33 2016 +0200 glusterd: set the maximum op-version for 3.8.0 release-3.8 was branched after the op-version was increased for version 4.0.0. The maximum op-version for GlusterFS 3.8.0 should be 30800. BUG: 1327174 Change-Id: Ia5796219d8fb115a680e6080f164d2c399d728a3 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: http://review.gluster.org/14551 Reviewed-by: Shyamsundar Ranganathan <srangana> NetBSD-regression: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Smoke: Gluster Build System <jenkins.com>
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.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user