Bug 1415245

Summary:	core: max op version
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	core	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	amukherj, bugs, srangana
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-15 13:54:20 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:
Bug Blocks:	1416031

Description Kaleb KEITHLEY 2017-01-20 16:29:42 UTC

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):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-01-20 16:31:58 UTC

REVIEW: http://review.gluster.org/16447 (glusterd: set maximum supported op-version) posted (#2) for review on release-3.10 by Kaleb KEITHLEY (kkeithle)

Comment 2 Atin Mukherjee 2017-01-20 16:36:25 UTC

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.

Comment 3 Worker Ant 2017-01-24 15:21:22 UTC

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 (kkeithle)

Comment 4 Worker Ant 2017-01-25 13:56:44 UTC

COMMIT: https://review.gluster.org/16465 committed in release-3.10 by Shyamsundar Ranganathan (srangana) 
------
commit 34213d9f34df15dbec42e389f327a893799f1c75
Author: Kaleb S. KEITHLEY <kkeithle>
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
    
    BUG: 1415245
    Change-Id: I37edef6ab67e4ef64adbd02266942a8e4c5484c5
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: https://review.gluster.org/16465
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Shyamsundar Ranganathan <srangana>
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>

Comment 5 Shyamsundar 2017-03-06 17:44:03 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-3.10.0, please open a new bug report.

glusterfs-3.10.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/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/