[Bugs] [Bug 1229263] 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=1229263

            Bug ID: 1229263
           Summary: Data Tiering:do not allow detach-tier when the volume
                    is in "stopped" status
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs
     Sub Component: tiering
          Severity: urgent
          Priority: urgent
          Assignee: rhs-bugs at redhat.com
          Reporter: nchilaka at redhat.com
        QA Contact: nchilaka at redhat.com
                CC: bugs at gluster.org, josferna at redhat.com,
                    rkavunga at redhat.com, vagarwal at redhat.com
        Depends On: 1216976
            Blocks: 1186580 (qe_tracker_everglades)



+++ This bug was initially created as a clone of Bug #1216976 +++

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

--- Additional comment from Mohammed Rafi KC on 2015-05-02 09:59:07 EDT ---

Fixed as part of the change http://review.gluster.org/#/c/10284/.

--- Additional comment from Niels de Vos on 2015-05-15 09:07:42 EDT ---

This change should not be in "ON_QA", the patch posted for this bug is only
available in the master branch and not in a release yet. Moving back to
MODIFIED until there is an beta release for the next GlusterFS version.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1186580
[Bug 1186580] QE tracker bug for Everglades
https://bugzilla.redhat.com/show_bug.cgi?id=1216976
[Bug 1216976] Data Tiering:do not allow detach-tier when the volume is in
"stopped" status
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=IZZBHxP5xj&a=cc_unsubscribe