gluster volume detach-tier needs meaningful o/p. This is the current o/p for gluster vol detach-tier "Volume detach-tier failed" This does not tell anything. The o/p here needs to be more informative and tell things like ; detach for which volume, usage etc.
Another o/p which needs refinement is o/p for sucessful detach. This is how it looks like today: [root@dhcp35-56 gfs]# gluster vol detach-tier vol1 volume remove-brick unknown: success Above o/p does not make sense.
Another one: [root@dhcp35-56 ~]# gluster vol attach-tier vol1 replica 2 10.70.35.56:/rhs/brick5 10.70.35.67:/rhs/brick5 force volume add-brick: success Why should attach tier give "volume add-brick: success"? It should be more meaningful, something like, "tier attach: success" and also info on which volume it is getting attached to.
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.
Rafi, you moved this bug ASSIGNED -> POST -> MODIFIED. I can not find a change in Gerrit addresses this bug. Is this bug a duplicate of an other? Or can you post the link to the change so that I can review my search/check/compare workflow?
Included the changes as part of another bug, Patch for the change is : http://review.gluster.org/#/c/10713/
(In reply to Mohammed Rafi KC from comment #5) > Included the changes as part of another bug, Patch for the change is : > http://review.gluster.org/#/c/10713/ http://review.gluster.org/10284 is the original patch for the master branch: cli/tiering: Enhance cli output for tiering Fix for handling cli output for attach-tier and detach-tier Change-Id: I4d17f4b09612754fe1b8cec6c2e14927029b9678 BUG: 1211562 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/10284 Reviewed-by: Dan Lambright <dlambrig> Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System Reviewed-by: Vijay Bellur <vbellur> *** This bug has been marked as a duplicate of bug 1211562 ***