Bug 1291603

Summary: [tiering]: read/write freq-threshold allows negative values
Product: [Community] GlusterFS Reporter: Joseph Elwin Fernandes <josferna>
Component: tieringAssignee: Joseph Elwin Fernandes <josferna>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: bugs, kramdoss, mselvaga, nchilaka, sankarshan
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.8rc2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1291052
: 1292359 (view as bug list) Environment:
Last Closed: 2016-06-16 13:50:45 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: 1291052    
Bug Blocks: 1292359    

Comment 1 Vijay Bellur 2015-12-15 09:15:25 UTC
REVIEW: http://review.gluster.org/12970 (tier/glusterd: Only positive values for freq-thresholds) posted (#2) for review on master by Joseph Fernandes

Comment 2 Vijay Bellur 2015-12-16 03:08:45 UTC
REVIEW: http://review.gluster.org/12970 (tier/glusterd: Only positive values for freq-thresholds) posted (#3) for review on master by Joseph Fernandes

Comment 3 Vijay Bellur 2015-12-16 14:45:34 UTC
COMMIT: http://review.gluster.org/12970 committed in master by Dan Lambright (dlambrig) 
------
commit 4eb7c968a682e59d97efcbc2afa41690dfdd22a2
Author: Joseph Fernandes <josferna>
Date:   Tue Dec 15 14:39:25 2015 +0530

    tier/glusterd: Only positive values for freq-thresholds
    
    Fixed error handling for validation for freq-thresholds
    
    Change-Id: Ibe3a9752ac0b525b0c8c0d6c4b4e4d694bd91b88
    BUG: 1291603
    Signed-off-by: Joseph Fernandes <josferna>
    Reviewed-on: http://review.gluster.org/12970
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: Dan Lambright <dlambrig>

Comment 4 Niels de Vos 2016-06-16 13:50:45 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