Description of problem: Operations like detach-tier commit gives success for a non-tiered volume also Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.create a tired volume 2.detach the tier 3.again try to detach (detach-tier commit) Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/10773 (tier: Do not allow detach-tier commands on a non-tiered volume) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/10773 (tier: Do not allow detach-tier commands on a non-tiered volume) posted (#2) for review on master by mohammed rafi kc (rkavunga)
COMMIT: http://review.gluster.org/10773 committed in master by Kaushal M (kaushal) ------ commit 3cb713f2aec3c2191cf8fd2df830b92bf3ad92d4 Author: Mohammed Rafi KC <rkavunga> Date: Wed May 13 20:33:45 2015 +0530 tier: Do not allow detach-tier commands on a non-tiered volume Change-Id: Ic92d25db68e40ef4a4388ef42affd1b3ee5a7ec6 BUG: 1221270 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/10773 Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Raghavendra G <rgowdapp> Reviewed-by: Kaushal M <kaushal> Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System
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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user