Post branching 4.1 the op-version was moved to 4.2 as usual, but over the course, the movement of release numbers makes this incorrect, and this needs to be changed to 5.0 across.
REVIEW: https://review.gluster.org/21172 (glusterd: Update op-version from 4.2 to 5.0) posted (#1) for review on master by Shyamsundar Ranganathan
COMMIT: https://review.gluster.org/21172 committed in master by "Shyamsundar Ranganathan" <srangana> with a commit message- glusterd: Update op-version from 4.2 to 5.0 Post changing the max op-version to 4.2, after release 4.1 branching, the decision was to go with increasing release numbers. Thus this needs to change to 5.0. This commit addresses the above change. Fixes: bz#1628664 Change-Id: Ifcc0c6da90fdd51e4eceea40749511110a432cce 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-6.0, please open a new bug report. glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/