Bug 1289898

Summary:	Without detach tier commit, status changes back to tier migration
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	tiering	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.7.6	CC:	bugs, byarlaga, dlambrig, nchilaka, rcyriac, rkavunga, sankarshan
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1286974	Environment:
Last Closed:	2016-04-19 07:50:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1284387, 1286974
Bug Blocks:

Comment 1 Vijay Bellur 2015-12-09 10:04:38 UTC

REVIEW: http://review.gluster.org/12921 (tier/glusterd: Check before starting tier daemon during volume start) posted (#2) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 2 Vijay Bellur 2015-12-10 09:06:28 UTC

REVIEW: http://review.gluster.org/12921 (tier/glusterd: Check before starting tier daemon during volume start) posted (#3) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 3 Vijay Bellur 2015-12-11 18:52:23 UTC

COMMIT: http://review.gluster.org/12921 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit 6746376747b0a06def2faff1b6af4b8bd624ed55
Author: Mohammed Rafi KC <rkavunga>
Date:   Tue Dec 1 09:11:01 2015 +0000

    tier/glusterd: Check before starting tier daemon during volume start
    
    We start tier daemon when volume is started without looking into the
    previous status. The problem with that if detach-tier is started
    and then volume force start is actually starting tier daemon.
    
    This is also fixes a problem where tier daemon is not starting
    after detach stop.
    
    Back port of>
    >Change-Id: I15b56a711e12f0e24f5ab123561258bd448621f7
    >BUG: 1286974
    >Signed-off-by: Mohammed Rafi KC <rkavunga>
    >Reviewed-on: http://review.gluster.org/12833
    >Tested-by: NetBSD Build System <jenkins.org>
    >Tested-by: Gluster Build System <jenkins.com>
    >Reviewed-by: Atin Mukherjee <amukherj>
    
    (cherry picked from commit 28da53e26e88f23f8917810ce0177f2628aa7e9a)
    
    Change-Id: I22c9ad0b2bc4488c15978d8bf85d05113e8b886e
    BUG: 1289898
    Signed-off-by: Mohammed Rafi KC <rkavunga>
    Reviewed-on: http://review.gluster.org/12921
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Dan Lambright <dlambrig>

Comment 4 Kaushal 2016-04-19 07:50:21 UTC

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 [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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user