Description of problem: Current op-version 40000 is used for 4.0.0 and that has been branched. Enable the next op-version on master for the future release 40100, 4.1.0.
REVIEW: https://review.gluster.org/19388 (glusterd: Update op-version for master) posted (#1) for review on master by Shyamsundar Ranganathan
COMMIT: https://review.gluster.org/19388 committed in master by "Shyamsundar Ranganathan" <srangana> with a commit message- glusterd: Update op-version for master Updated the op-version on master to the next release op-version, for any future options appearing on master. Change-Id: I2ef6f8874c638ade1d97477bdd8ffa1bd1a9f952 BUG: 1540338 Signed-off-by: ShyamsundarR <srangana>
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-v4.1.0, please open a new bug report. glusterfs-v4.1.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://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/