Bug 1276018

Summary:	Wrong value of snap-max-hard-limit observed in 'gluster volume info'.
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	asengupt, asrivast, bugs, byarlaga, rjoseph, sraj, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1275521
Clones:	1277394 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:41:47 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:	1275521
Bug Blocks:	1277394

Comment 1 Vijay Bellur 2015-10-28 12:18:23 UTC

REVIEW: http://review.gluster.org/12443 (snapshot: Don't display snapshot's hard-limit and soft-limit in vol info) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Vijay Bellur 2015-11-03 06:34:41 UTC

COMMIT: http://review.gluster.org/12443 committed in master by Rajesh Joseph (rjoseph) 
------
commit 2e56bde3ea952beabd27cdf8a3a10da563a00bcc
Author: Avra Sengupta <asengupt>
Date:   Wed Oct 28 15:18:07 2015 +0530

    snapshot: Don't display snapshot's hard-limit and soft-limit in vol info
    
    The snap-max-hard-limit being displayed in the volume info
    currently is propagated from system's snap-max-hard-limit as
    that is a global option common for all volumes, and hence ends
    up showing the system's snap-max-hard-limit.
    
    We should not be displaying snap-max-hard-limit and
    snap-max-soft-limit in the volume info at all, as these are
    snap config options and should be set and displayed via snap
    config command.
    
    Modified bug-1113476.t to test the same behaviour.
    
    Change-Id: I90891f0cf7fb39fd686787297c7f7cd8c1e7daa1
    BUG: 1276018
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/12443
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: mohammed rafi  kc <rkavunga>
    Reviewed-by: Rajesh Joseph <rjoseph>
    Tested-by: NetBSD Build System <jenkins.org>

Comment 3 Niels de Vos 2016-06-16 13:41:47 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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user