Description of problem:
The response user gets after executing a attach-tier or detach-tier right now are quite ambigous. They talk about brick rather than the tier.
Eg: on a attach tier it says "add-brick is success"
[root@yarrow ~]# gluster v attach-tier ec_vol1 yarrow:/yarrow_ssd_75G_2/ec_vol1 rhs-client6:/brick15/ec_vol1 force
volume add-brick: success
[root@yarrow ~]# gluster v info ec_vol1
It should instead say, attaching of tier to <volname> is successful
same with detach tier, it say remove-brick is success
Need to take care even when the command fails, like it should be detach-tier fails rather than remove-brick fails
Version-Release number of selected component (if applicable):
[root@yarrow ~]# gluster --version
glusterfs 3.7dev built on Apr 8 2015 17:57:45
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 ~]# rpm -qa|grep gluster
always and easily
Steps to Reproduce:
1.create a regular volume
2.attach a tier, the reponse user gets talks abt brick rather than tier
3.same with detaching the tier
REVIEW: http://review.gluster.org/10284 (cli/tiering: Enhance cli output for tiering) posted (#1) for review on master by mohammed rafi kc (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/10284 (cli/tiering: Enhance cli output for tiering) posted (#2) for review on master by mohammed rafi kc (email@example.com)
REVIEW: http://review.gluster.org/10284 (cli/tiering: Enhance cli output for tiering) posted (#5) for review on master by mohammed rafi kc (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/10284 committed in master by Vijay Bellur (email@example.com)
Author: Mohammed Rafi KC <firstname.lastname@example.org>
Date: Sat May 2 17:31:07 2015 +0530
cli/tiering: Enhance cli output for tiering
Fix for handling cli output for attach-tier and
Signed-off-by: Mohammed Rafi KC <email@example.com>
Reviewed-by: Dan Lambright <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Tested-by: NetBSD Build System
Reviewed-by: Vijay Bellur <firstname.lastname@example.org>
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.
*** Bug 1214273 has been marked as a duplicate of this bug. ***
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.