Bug 1238135

Summary:	Initialize daemons on demand
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, kaushal
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1247012 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:18:34 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:
Bug Blocks:	1247012

Description Atin Mukherjee 2015-07-01 09:33:31 UTC

Description of problem:

As of now all the daemon services are initialized at glusterD init path. Since
socket file path of per node daemon demands the uuid of the node, MY_UUID macro
is invoked as part of the initialization. This flow breaks the usecases where a gluster image is built following a template (it could be Dockerfile, vagrantfile or any kind of virtualization environment). This means bringing instances of this image would have same UUIDs for the node resulting in peer probe failure.


Version-Release number of selected component (if applicable):
Mainline

How reproducible:
Always

Steps to Reproduce:
1. Build a docker image using https://registry.hub.docker.com/u/gluster/gluster-fedora/dockerfile/ 
2. Bring up multiple containers using the above image
3. Check the UUIDs on all these containers by cat /var/lib/glusterd/glusterd.info | grep UUID

Actual results:
UUIDs are same

Expected results:
UUIDs should be unique.

Additional info:

Comment 1 Anand Avati 2015-07-01 09:41:44 UTC

REVIEW: http://review.gluster.org/11488 (glusterd: initialize the daemon services on demand) posted (#2) for review on master by Atin Mukherjee (amukherj)

Comment 2 Anand Avati 2015-07-01 10:03:48 UTC

REVIEW: http://review.gluster.org/11488 (glusterd: initialize the daemon services on demand) posted (#3) for review on master by Atin Mukherjee (amukherj)

Comment 3 Anand Avati 2015-07-01 12:05:32 UTC

REVIEW: http://review.gluster.org/11488 (glusterd: initialize the daemon services on demand) posted (#4) for review on master by Atin Mukherjee (amukherj)

Comment 4 Anand Avati 2015-07-02 10:39:48 UTC

REVIEW: http://review.gluster.org/11488 (glusterd: initialize the daemon services on demand) posted (#5) for review on master by Atin Mukherjee (amukherj)

Comment 5 Anand Avati 2015-07-06 10:52:15 UTC

REVIEW: http://review.gluster.org/11488 (glusterd: initialize the daemon services on demand) posted (#6) for review on master by Atin Mukherjee (amukherj)

Comment 6 Anand Avati 2015-07-08 03:57:16 UTC

REVIEW: http://review.gluster.org/11488 (glusterd: initialize the daemon services on demand) posted (#7) for review on master by Atin Mukherjee (amukherj)

Comment 7 Anand Avati 2015-07-13 04:31:47 UTC

REVIEW: http://review.gluster.org/11488 (glusterd: initialize the daemon services on demand) posted (#8) for review on master by Atin Mukherjee (amukherj)

Comment 8 Anand Avati 2015-07-23 04:10:01 UTC

REVIEW: http://review.gluster.org/11488 (glusterd: initialize the daemon services on demand) posted (#9) for review on master by Atin Mukherjee (amukherj)

Comment 9 Nagaprasad Sathyanarayana 2015-10-25 14:56:17 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 10 Niels de Vos 2016-06-16 13:18:34 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.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