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@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@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
Fixed as part of the change http://review.gluster.org/#/c/10284/.
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.
This bug was ON_QA status, and on GlusterFS product in bugzilla, we don't have that as a valid status. We are closing it as 'CURRENT RELEASE ' to indicate the availability of the fix, please reopen if found again.