Bug 1086141

Summary:	"glusterd" service does not start automatically after reboots
Product:	[Community] GlusterFS	Reporter:	Bala.FA <barumuga>
Component:	build	Assignee:	Bala.FA <barumuga>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs, dpati, gluster-bugs, grajaiya, nlevinki, nsathyan, rcyriac, rhs-bugs, spandura, vagarwal
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1081899	Environment:
Last Closed:	2014-11-11 08:29:47 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:	1081899
Bug Blocks:

Comment 1 Anand Avati 2014-04-10 08:39:33 UTC

REVIEW: http://review.gluster.org/7432 (build: set run levels for glusterd init script properly) posted (#1) for review on master by Bala FA (barumuga)

Comment 2 Anand Avati 2014-04-13 06:03:23 UTC

COMMIT: http://review.gluster.org/7432 committed in master by Vijay Bellur (vbellur) 
------
commit c193996c94901d81a2a623799d83ef96f595d3e2
Author: Bala.FA <barumuga>
Date:   Thu Apr 10 14:03:55 2014 +0530

    build: set run levels for glusterd init script properly
    
    'chkconfig --add glusterd' does not set run levels for start/stop.
    This patch fixes it.
    
    Change-Id: I8962f5207d034b6875353e15eb60c4d08c5a4fe4
    BUG: 1086141
    Signed-off-by: Bala.FA <barumuga>
    Reviewed-on: http://review.gluster.org/7432
    Reviewed-by: Niels de Vos <ndevos>
    Tested-by: Gluster Build System <jenkins.com>

Comment 3 Niels de Vos 2014-09-22 12:37:52 UTC

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:29:47 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users