Red Hat Bugzilla – Bug 1279637
Data Tiering:Regression:Detach tier commit is passing when detach tier is in progress
Last modified: 2016-06-16 09:43:35 EDT
+++ 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
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 (firstname.lastname@example.org)
--- 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 (email@example.com)
http://review.gluster.org/#/c/12560/ posted for review
COMMIT: http://review.gluster.org/12560 committed in master by Dan Lambright (firstname.lastname@example.org)
Author: Dan Lambright <email@example.com>
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.
Signed-off-by: Dan Lambright <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Atin Mukherjee <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.8.0, please open a new bug report.
glusterfs-3.8.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.