Bug 1628668 - Update op-version from 4.2 to 5.0
Summary: Update op-version from 4.2 to 5.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Shyamsundar
QA Contact:
URL:
Whiteboard:
Depends On: 1628664
Blocks: glusterfs-5.0
TreeView+ depends on / blocked
 
Reported: 2018-09-13 16:58 UTC by Shyamsundar
Modified: 2018-10-23 15:19 UTC (History)
1 user (show)

Fixed In Version: glusterfs-5.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1628664
Environment:
Last Closed: 2018-10-23 15:19:00 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Shyamsundar 2018-09-13 16:58:11 UTC
+++ This bug was initially created as a clone of Bug #1628664 +++

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.

--- Additional comment from Worker Ant on 2018-09-13 12:55:48 EDT ---

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

Comment 1 Worker Ant 2018-09-14 14:32:16 UTC
REVIEW: https://review.gluster.org/21181 (glusterd: Update op-version from 4.2 to 5.0) posted (#1) for review on release-5 by Shyamsundar Ranganathan

Comment 2 Worker Ant 2018-09-17 14:27:19 UTC
COMMIT: https://review.gluster.org/21181 committed in release-5 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#1628668
Change-Id: Ifcc0c6da90fdd51e4eceea40749511110a432cce
Signed-off-by: ShyamsundarR <srangana>

Comment 3 Shyamsundar 2018-10-23 15:19:00 UTC
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-5.0, please open a new bug report.

glusterfs-5.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/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.