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

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

nchilaka <nchilaka at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ON_QA                       |VERIFIED



--- Comment #3 from nchilaka <nchilaka at redhat.com> ---
working as expected, hence moving to fixed

[root at zod ~]# gluster v detach-tier ctr_set 
Usage: volume detach-tier <VOLNAME>  <start|stop|status|commit|force>
Tier command failed
[root at zod ~]# gluster v detach-tier ctr_set start force
Usage: volume detach-tier <VOLNAME>  <start|stop|status|commit|force>
Tier command failed
[root at zod ~]# gluster v detach-tier ctr_set force
Removing tier can result in data loss. Do you want to Continue? (y/n) n
[root at zod ~]# gluster v stop ctr_set
Stopping volume will make its data inaccessible. Do you want to continue? (y/n)
y
volume stop: ctr_set: failed: Volume ctr_set is not in the started state
[root at zod ~]# gluster v detach-tier ctr_set start force
Usage: volume detach-tier <VOLNAME>  <start|stop|status|commit|force>
Tier command failed
[root at zod ~]# gluster v detach-tier ctr_set start
volume detach-tier start: failed: Volume ctr_set needs to be started before
detach-tier (you can use 'force' or 'commit' to override this behavior)
Tier command failed
[root at zod ~]#

-- 
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=Z4kUk9Ei9q&a=cc_unsubscribe