[Bugs] [Bug 1216976] New: Data Tiering:do not allow detach-tier when the volume is in "stopped" status

[bugzilla at redhat.com]

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

            Bug ID: 1216976
           Summary: Data Tiering:do not allow detach-tier when the volume
                    is in "stopped" status
           Product: GlusterFS
           Version: mainline
         Component: tiering
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:
=======================
currently detach-tier executes successfully straight away on a stopped volume.
We should not be allowing this. The user could have stopped the volume for some
maintanace purpose.
In case we want to allow, then let the user use force option just like with a
remove-brick

Allowing straight away can cause data loss with accidental issue of detach-tier
command



Version-Release number of selected component (if applicable):
==========================================================
[root at yarrow glusterfs]# gluster --version
glusterfs 3.7.0alpha0 built on Apr 28 2015 01:37:11
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.
[root at yarrow glusterfs]# rpm -qa|grep gluster
glusterfs-fuse-3.7.0alpha0-0.17.gited96153.el7.centos.x86_64
glusterfs-libs-3.7.0alpha0-0.17.gited96153.el7.centos.x86_64
glusterfs-3.7.0alpha0-0.17.gited96153.el7.centos.x86_64
glusterfs-cli-3.7.0alpha0-0.17.gited96153.el7.centos.x86_64
glusterfs-server-3.7.0alpha0-0.17.gited96153.el7.centos.x86_64
glusterfs-api-3.7.0alpha0-0.17.gited96153.el7.centos.x86_64



Steps to Reproduce:
===================
1.create a volume and start it and attach tier to it
2.now stop the volume 
3.issue a detach tier. this passes straight away



Expected results:
==================
don't allow detach-tier on a stopped volume.
Incase we have to allow, let it be with force option, just as in remove brick
Allowing straight away can cause data loss with accidental issue of detach-tier
command

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