Bug 1275910

Summary:	[Tier]: Typo in the output while setting the wrong value of low/hi watermark
Product:	[Community] GlusterFS	Reporter:	hari gowtham <hgowtham>
Component:	tiering	Assignee:	hari gowtham <hgowtham>
Status:	CLOSED EOL	QA Contact:	bugs <bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.7.5	CC:	bugs, dlambrig, nchilaka, rhinduja, rhs-bugs, sankarshan
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1275502	Environment:
Last Closed:	2017-03-08 10:59:59 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:	1275155, 1275502
Bug Blocks:

Comment 1 Vijay Bellur 2015-10-28 06:15:24 UTC

REVIEW: http://review.gluster.org/12434 (tier: Typo while setting the wrong value of low/hi watermark) posted (#2) for review on release-3.7 by hari gowtham (hari.gowtham005)

Comment 2 Vijay Bellur 2015-10-28 11:20:20 UTC

COMMIT: http://review.gluster.org/12434 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit c926dcf3a76ae5caeaa5dacc4210949bc3f8f212
Author: hari gowtham <hgowtham>
Date:   Tue Oct 27 11:51:33 2015 +0530

    tier: Typo while setting the wrong value of low/hi watermark
    
            back port of : http://review.gluster.org/#/c/12432/
    
    While setting the wrong value of watermark-hi/low the output
    shows "compatiblevalue" whereas it should be "compatible value"
    
    >Change-Id: I29c8f9a954928d22e436465f4ebc30bd08640138
    >BUG: 1275502
    >Signed-off-by: hari gowtham <hgowtham>
    >Reviewed-on: http://review.gluster.org/12432
    >Reviewed-by: Humble Devassy Chirammal <humble.devassy>
    >Tested-by: Gluster Build System <jenkins.com>
    >Reviewed-by: Dan Lambright <dlambrig>
    
    Change-Id: I29c8f9a954928d22e436465f4ebc30bd08640138
    BUG: 1275910
    Reviewed-on: http://review.gluster.org/12434
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

Comment 3 Kaushal 2017-03-08 10:59:59 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.