+++ This bug was initially created as a clone of Bug #1264441 +++ when detach tier is in progress, detach tier commit must not be allowed. This was working well previously. This means it is a regression, Could be due to fix for bz#1259694 glusterfs-server-3.7.4-0.33.git1d02d4b.el7.centos.x86_64 Steps to Reproduce: ==================== 1.create a volume, start it and attac tier to vol and create lot of data on hot tier 2.now issue a detach-tier <vname> start 3. While it is in progress,issue a detach-tier <vname> commit --- Additional comment from nchilaka on 2015-09-18 09:21:39 EDT --- this wasfound during automation of qe scripts --- Additional comment from Dan Lambright on 2015-09-30 15:36:21 EDT --- have done a RCA on this and will begin working on a fix. --- Additional comment from Dan Lambright on 2015-10-01 11:14:45 EDT --- submitted fix 12272 --- Additional comment from Vijay Bellur on 2015-10-28 12:44:33 EDT --- REVIEW: http://review.gluster.org/12272 (cluster/tier: migration daemon incorrectly signals detach tier done) posted (#3) for review on release-3.7 by Dan Lambright (dlambrig) --- Additional comment from Vijay Bellur on 2015-10-28 16:31:24 EDT --- REVIEW: http://review.gluster.org/12272 (cluster/tier: Disallow detach commit when detach in progress) posted (#4) for review on release-3.7 by Dan Lambright (dlambrig)
http://review.gluster.org/#/c/12560/ posted for review
COMMIT: http://review.gluster.org/12560 committed in master by Dan Lambright (dlambrig) ------ commit 6000e1aa344e523aa161427a0b9781e052cd4d97 Author: Dan Lambright <dlambrig> Date: Thu Oct 1 11:05:25 2015 -0400 cluster/tier: Disallow detach commit when detach in progress 1. Check if detach is running, disallow detach commit if so. 2. Cleanup shutdown of tier daemon on detach: do not rerun fix-layout, do not send incorrect status back to glusterd. Change-Id: I97202f748773c1176396a4ffd32a4c7fa9b9c1bc BUG: 1279637 Signed-off-by: Dan Lambright <dlambrig> Reviewed-on: http://review.gluster.org/12560 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj>
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