[Bugs] [Bug 1271724] New: Data Tiering: detach-tier start force command not available on a tier volume(unlike which is possible in force remove-brick)

Wed Oct 14 14:35:53 UTC 2015

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

            Bug ID: 1271724
           Summary: Data Tiering: detach-tier start  force  command not
                    available on a tier volume(unlike which is possible in
                    force remove-brick)
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs
     Sub Component: tiering
          Keywords: Triaged
          Severity: low
          Priority: low
          Assignee: rhs-bugs at redhat.com
          Reporter: rkavunga at redhat.com
        QA Contact: nchilaka at redhat.com
                CC: bugs at gluster.org, nchilaka at redhat.com,
                    rkavunga at redhat.com, vagarwal at redhat.com
        Depends On: 1258242
            Blocks: 1260923, 1261862

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

Description of problem:
======================
There is no detach-tier start force command available, eventhough it shows in
the help.
For eg, offline a tier volume and then issue a detach-tier. It fails saying
below:
root at nag-manual-node1 ~]# gluster v detach-tier testme start
volume detach-tier start: failed: Volume testme needs to be started before
remove-brick (you can use 'force' or 'commit' to override this behavior)

but,When we try to do a force detach-tier start on an offline volume, it doesnt
succeed.It still throws same error:
[root at nag-manual-node1 ~]# gluster v detach-tier testme start force
volume detach-tier start: failed: Volume testme needs to be started before
remove-brick (you can use 'force' or 'commit' to override this behavior)

Given that this part of code is taken from remove-brick.
On a regular volume when we do a force remove-brick start, it does start the
remove-brick process

hence there is difference in behavior here.

Remove-brick on an offline regular vol:
==============================
Volume Name: test2
Type: Distribute
Volume ID: 7357f734-6ba3-4f9a-b707-8b1defc82459
Status: Created
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 10.70.47.29:/rhs/brick1/test2
Brick2: 10.70.47.29:/rhs/brick2/test2
Options Reconfigured:
performance.readdir-ahead: on
[root at localhost ~]# gluster  v stop hello
Stopping volume will make its data inaccessible. Do you want to continue? (y/n)
n
[root at localhost ~]# gluster v stop test2
Stopping volume will make its data inaccessible. Do you want to continue? (y/n)
y
volume stop: test2: failed: Volume test2 is not in the started state

[root at localhost ~]# gluster v remove-brick test2 10.70.47.29:/rhs/brick1/test2
start
volume remove-brick start: failed: Volume test2 needs to be started before
remove-brick (you can use 'force' or 'commit' to override this behavior)
[root at localhost ~]# gluster v remove-brick test2 10.70.47.29:/rhs/brick1/test2
start force
wrong brick type: start, use <HOSTNAME>:<export-dir-abs-path>
Usage: volume remove-brick <VOLNAME> [replica <COUNT>] <BRICK> ...
<start|stop|status|commit|force>
[root at localhost ~]# gluster v remove-brick test2 10.70.47.29:/rhs/brick1/test2
force
Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: success

Detach-tier on an offline volume
==============================
[root at nag-manual-node1 ~]# gluster v detach-tier testme start
volume detach-tier start: failed: Volume testme needs to be started before
remove-brick (you can use 'force' or 'commit' to override this behavior)
[root at nag-manual-node1 ~]# gluster v detach-tier testme start force
volume detach-tier start: failed: Volume testme needs to be started before
remove-brick (you can use 'force' or 'commit' to override this behavior)
[root at nag-manual-node1 ~]# 
[root at nag-manual-node1 ~]# 

Version-Release number of selected component (if applicable):
==========================================================
[root at nag-manual-node1 ~]# gluster --version
glusterfs 3.7.3 built on Aug 27 2015 01:23:05
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 nag-manual-node1 ~]# rpm -qa|grep gluster
glusterfs-libs-3.7.3-0.82.git6c4096f.el6.x86_64
glusterfs-fuse-3.7.3-0.82.git6c4096f.el6.x86_64
glusterfs-server-3.7.3-0.82.git6c4096f.el6.x86_64
glusterfs-3.7.3-0.82.git6c4096f.el6.x86_64
glusterfs-api-3.7.3-0.82.git6c4096f.el6.x86_64
glusterfs-cli-3.7.3-0.82.git6c4096f.el6.x86_64
python-gluster-3.7.3-0.82.git6c4096f.el6.noarch

How reproducible:

Steps to Reproduce:
1.offline a tier volume
2.issue a detach-tier start
3.it will fail saying use force or commit
4. try using force, it will still throw same error thrown in step#2

--- Additional comment from Vivek Agarwal on 2015-10-01 08:12:52 EDT ---

 http://review.gluster.org/12151 merged in the master

Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1258242
[Bug 1258242] Data Tiering: detach-tier start  force  command not available
on a tier volume(unlike which is possible in force remove-brick)
https://bugzilla.redhat.com/show_bug.cgi?id=1260923
[Bug 1260923] Tracker for tiering in 3.1.2
https://bugzilla.redhat.com/show_bug.cgi?id=1261862
[Bug 1261862] Data Tiering: detach-tier start  force  command not available
on a tier volume(unlike which is possible in force remove-brick)
-- 
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=SEdTBP6Az2&a=cc_unsubscribe