Bug 1279351

Summary:	[GlusterD]: Volume start fails post add-brick on a volume which is not started
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	glusterd	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.6	CC:	amukherj, bsrirama, bugs, dlambrig, nlevinki, rhs-bugs, rkavunga, vbellur
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1279319
Clones:	1282322 (view as bug list)		Environment:
Last Closed:	2016-04-19 07:47:50 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:	1279319
Bug Blocks:	1282322

Comment 1 Vijay Bellur 2015-11-16 11:24:25 UTC

REVIEW: http://review.gluster.org/12585 (glusterd: brick failed to start) posted (#1) for review on release-3.7 by mohammed rafi  kc (rkavunga)

Comment 2 Vijay Bellur 2015-11-16 14:18:03 UTC

COMMIT: http://review.gluster.org/12585 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit cc7367bcde55c315a299aa97d521d25424f15e76
Author: Mohammed Rafi KC <rkavunga>
Date:   Mon Nov 9 16:43:21 2015 +0530

    glusterd: brick failed to start
    
    brick volfiles are generated in post validate, if
    it is running version higher than GLUSTER_3_7_5,
    else will be running in syncop.
    
    If the code fall back to syncop, and volume is stopped
    then we were returning the operation with out generating
    volfiles.
    
    back port of >
    >Change-Id: I3b16ee29de19c5d34e45d77d6b7e4b665c2a4653
    >BUG: 1282322
    >Signed-off-by: Mohammed Rafi KC <rkavunga>
    >Reviewed-on: http://review.gluster.org/12552
    >Tested-by: NetBSD Build System <jenkins.org>
    >Tested-by: Gluster Build System <jenkins.com>
    >Reviewed-by: Atin Mukherjee <amukherj>
    
    (cherry picked from commit 571cbcf56ef865d64ebdb1621c791fe467501e52)
    
    Change-Id: I3b16ee29de19c5d34e45d77d6b7e4b665c2a4653
    BUG: 1279351
    Reviewed-on: http://review.gluster.org/12585
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

Comment 3 Kaushal 2016-04-19 07:47:50 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