[Bugs] [Bug 1419868] removing old tier commands under the rebalance commands

[bugzilla at redhat.com]

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



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16555 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com) 
------
commit c13a39e6c425622221226e5a3c49aafbf430a07d
Author: hari gowtham <hgowtham at redhat.com>
Date:   Tue Jan 24 14:24:47 2017 +0530

    CLI/TIER: removing old tier commands under rebalance

            back-port of : https://review.gluster.org/#/c/16463/

    PROBLEM: gluster v rebalance <volname> tier start works even after
    the switch of tier to service framework.
    This lets the user have two tierd for the same volume.

    FIX: checking for each process will make the new code hard
    to maintain. So we are removing the support for old commands.

    >Change-Id: I5b0974b2dbb74f0bee8344b61c7f924300ad73f2
    >BUG: 1415590
    >Signed-off-by: hari gowtham <hgowtham at redhat.com>
    >Reviewed-on: https://review.gluster.org/16463
    >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: N Balachandran <nbalacha at redhat.com>
    >Reviewed-by: Atin Mukherjee <amukherj at redhat.com>

    Change-Id: Ib996d89b1bd250176a3f5eeb369b71b0a4f95968
    BUG: 1419868
    Signed-off-by: hari gowtham <hgowtham at redhat.com>
    Reviewed-on: https://review.gluster.org/16555
    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>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>

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