Bug 1315562

Summary:	setting lower op-version should throw failure message
Product:	[Community] GlusterFS	Reporter:	Gaurav Kumar Garg <ggarg>
Component:	glusterd	Assignee:	Gaurav Kumar Garg <ggarg>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.0	CC:	amukherj, bugs, mzywusko, nlevinki, rhinduja, sasundar, smohan, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1315186	Environment:
Last Closed:	2016-04-19 07:20:46 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:	1315186, 1330545
Bug Blocks:

Comment 1 Vijay Bellur 2016-03-08 05:20:06 UTC

REVIEW: http://review.gluster.org/13635 (glusterd: avoid setting op-version lower than current cluster op-version) posted (#1) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

Comment 2 Vijay Bellur 2016-03-09 02:18:18 UTC

COMMIT: http://review.gluster.org/13635 committed in release-3.7 by Vijay Bellur (vbellur) 
------
commit d1272ef0fdc9897fa388665e039b9f713109ef0c
Author: Gaurav Kumar Garg <garg.gaurav52>
Date:   Mon Mar 7 13:37:31 2016 +0530

    glusterd: avoid setting op-version lower than current cluster op-version
    
    This patch is backport of: http://review.gluster.org/#/c/13622/
    
    Currently glusterd allow setting a cluster op-version which is lower than
    current cluster op-version. Though command is successful but it does not
    set that lower op-version.
    
    With this fix it will return error message "Required op-version
    (requested op-version) should not be lower than current cluster
    op-version (current cluster op-version)"
    
    Change-Id: Ia5b61858ee22a5a26721ec12ab12ff48e1a40c82
    BUG: 1315562
    Signed-off-by: Gaurav Kumar Garg <ggarg>
    
      >> Change-Id: Ia5b61858ee22a5a26721ec12ab12ff48e1a40c82
      >> BUG: 1315186
      >> Signed-off-by: Gaurav Kumar Garg <ggarg>
      >> Reviewed-on: http://review.gluster.org/13622
      >> Smoke: Gluster Build System <jenkins.com>
      >> CentOS-regression: Gluster Build System <jenkins.com>
      >> NetBSD-regression: NetBSD Build System <jenkins.org>
      >> Reviewed-by: Atin Mukherjee <amukherj>
    (cherry picked from commit 2d87a981657ee23d00c20813deddeb320e0afa8f)
    
    Change-Id: Ie75b2a0c43ab2c5a908f4d3800e1df62770d315b
    Reviewed-on: http://review.gluster.org/13635
    Tested-by: Gaurav Kumar Garg <ggarg>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Kaushal 2016-04-19 07:20:46 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.7.9, please open a new bug report.

glusterfs-3.7.9 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://www.gluster.org/pipermail/gluster-users/2016-March/025922.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user