Bug 1628668

Summary:	Update op-version from 4.2 to 5.0
Product:	[Community] GlusterFS	Reporter:	Shyamsundar <srangana>
Component:	glusterd	Assignee:	Shyamsundar <srangana>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1628664	Environment:
Last Closed:	2018-10-23 15:19:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1628664
Bug Blocks:	1628620

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/