Description of problem:
http://review.gluster.org/16283 added GD_OP_VERSION_3_10_0 (31000) but didn't change GD_OP_VERSION_MAX to match
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/16447 (glusterd: set maximum supported op-version) posted (#2) for review on release-3.10 by Kaleb KEITHLEY (email@example.com)
Just a note that there was nothing wrong in the patch mentioned in the bug description. The patch wasconmitted in mainline and hence there the max op version has to stay as 40000.
REVIEW: https://review.gluster.org/16465 (core (3.10): correct max op version for 3.10) posted (#1) for review on release-3.10 by Kaleb KEITHLEY (firstname.lastname@example.org)
COMMIT: https://review.gluster.org/16465 committed in release-3.10 by Shyamsundar Ranganathan (email@example.com)
Author: Kaleb S. KEITHLEY <firstname.lastname@example.org>
Date: Tue Jan 24 10:17:01 2017 -0500
core (3.10): correct max op version for 3.10
remove GD_OP_VERSION_4_0_0, set GS_OP_VERSION_MAX to 3_10_0
Signed-off-by: Kaleb S. KEITHLEY <email@example.com>
Reviewed-by: Atin Mukherjee <firstname.lastname@example.org>
Reviewed-by: Shyamsundar Ranganathan <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
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.10.0, please open a new bug report.
glusterfs-3.10.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.