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

bugzilla at redhat.com bugzilla at redhat.com
Sun Aug 30 13:44:41 UTC 2015


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

            Bug ID: 1258242
           Summary: Data Tiering: detach-tier start  force  command not
                    available on a tier volume(unlike which is possible in
                    force remove-brick)
           Product: GlusterFS
           Version: 3.7.3
         Component: tiering
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



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

-- 
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.


More information about the Bugs mailing list