Red Hat Bugzilla – Bug 1291970
Data Tiering: new set of gluster v tier commands not working as expected
Last modified: 2016-04-19 03:51:02 EDT
REVIEW: http://review.gluster.org/12976 (tier/glusterd : making new tier detach command throw warning) posted (#1) for review on release-3.7 by hari gowtham (email@example.com)
REVIEW: http://review.gluster.org/12976 (tier/glusterd : making new tier detach command throw warning) posted (#2) for review on release-3.7 by hari gowtham (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/12976 committed in release-3.7 by Dan Lambright (email@example.com)
Author: hari gowtham <firstname.lastname@example.org>
Date: Fri Dec 4 18:34:36 2015 +0530
tier/glusterd : making new tier detach command throw warning
back port of : http://review.gluster.org/#/c/12883/
For detach tier, the validation was done using the string "detach-tier"
but the new commands used has the string "tier". Making the string use
"tier" to compare, creates problem as the tier status and tier detach
have the keyword "tier". So tier detach and tier status were separated.
and strtok was used to prevent the condition from passing when the
volume name has a substring of "tier". (only the second word from the
string is got and checked if the feature is tier).
Problem: new detach tier command doesnt throw warnings like
"not a tier volume" or " detach tier not started" respectively
instead it prints empty output.
Fix: while validate the volume is checked if its a tiered volume
if yes it is checked if the detach tier is started, else a warning
is thrown respectively.
>Signed-off-by: hari gowtham <email@example.com>
>Tested-by: NetBSD Build System <firstname.lastname@example.org>
>Tested-by: Gluster Build System <email@example.com>
>Reviewed-by: Atin Mukherjee <firstname.lastname@example.org>
Signed-off-by: hari gowtham <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Reviewed-by: Dan Lambright <email@example.com>
Tested-by: Dan Lambright <firstname.lastname@example.org>
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.7.7, please open a new bug report.
glusterfs-3.7.7 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.