Description of problem: When detach tier commit is attempted before the tier-rebalance is complete, it fails with the following error message. # gluster v tier spiderman detach commit Removing tier can result in data loss. Do you want to Continue? (y/n) y volume detach-tier commit: failed: Brick's in Hot tier is not decommissioned yet. Use gluster volume detach-tier <VOLNAME> <start | commit | force> command instead Tier command failed The following portion of the error message isn't clear. Use gluster volume detach-tier <VOLNAME> <start | commit | force> command instead We should ask the user either to wait till tier-rebalance is complete or use force option to forcefully detach the tier Version-Release number of selected component (if applicable): glusterfs-3.7.9-5.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. On a tiered volume, run detach tier commit before running detach tier start
will change the message to volume detach tier commit: failed: Bricks in hot tier are not decommissioned yet. Use gluster volume tier <VOLNAME> detach start
fixed by https://review.gluster.org/#/c/13365/ (master)
As tier is not being actively developed, I'm closing this bug. Feel free to open it if necessary.