+++ This bug was initially created as a clone of Bug #1374412 +++
Description of problem:
Detach tier commit operation should not be allowed when detach tier start operation has gone into failed state. There might be files which are not moved from hot to cold tier when a detach tier operation fails. Allowing to commit the operation removes off the hot tier bricks, thereby making those data in hot tier inaccessible.
Version-Release number of selected component (if applicable):
rpm -qa | grep 'gluster'
Steps to Reproduce:
1. create a tier vol and start detach tier operation
2. kill a brick on hot tier and restore it after a while to fail the detach tier operation
3. Try detach tier commit
detach tier commit is allowed
detach tier commit should not be allowed
REVIEW: http://review.gluster.org/15438 (Tier: failing detach commit on detach failure and in-progress) posted (#1) for review on master by hari gowtham (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/15438 (Tier: failing detach commit on detach failure and in-progress) posted (#2) for review on master by hari gowtham (email@example.com)
COMMIT: http://review.gluster.org/15438 committed in master by Dan Lambright (firstname.lastname@example.org)
Author: hari gowtham <email@example.com>
Date: Fri Sep 9 12:26:52 2016 +0530
Tier: failing detach commit on detach failure and in-progress
PROBLEM: if detach status has failed or if it remains in progress
we allow detach commit to happen. only detach force should
FIX: check the detach status for failure or inprogress and disallow
with the apt error message.
Signed-off-by: hari gowtham <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
Tested-by: hari gowtham <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
CentOS-regression: Gluster 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.10.0, please open a new bug report.
glusterfs-3.10.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.