[Bugs] [Bug 1328342] [tiering]: gluster v reset of watermark levels can allow low watermark level to have a higher value than hi watermark level

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1328342



--- Comment #8 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/14028 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 78222bff29f27fc3b4f500ff2f7bd323c418d09e
Author: hari gowtham <hgowtham at redhat.com>
Date:   Tue Apr 19 14:01:09 2016 +0530

    TIER: watermark check during low watermark reset

    PROBLEM: during a low watermark reset, checking of whether
    the low watermark is lower than hi watermark is not done.

    FIX: This patch checks if the hi watermark value is higher
    the default low watermark. Else throws an failure of the reset
    command

    Change-Id: I8b49090c6bccce6d45c2e8076ab766047a2a6162
    BUG: 1328342
    Signed-off-by: hari gowtham <hgowtham at redhat.com>
    Reviewed-on: https://review.gluster.org/14028
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Tested-by: hari gowtham <hari.gowtham005 at gmail.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.