From d49b4b1086119873664b77ea7d7f2a5dd8f671ee Mon Sep 17 00:00:00 2001 From: Atin Mukherjee Date: Wed, 1 Jul 2015 14:47:48 +0530 Subject: glusterd: initialize the daemon services on demand 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. The above flow breaks the usecases where a gluster image is built following a template 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. Solution is to lazily initialize the services on demand. Change-Id: If7caa533026c83e98c7c7678bded67085d0bbc1e BUG: 1238135 Signed-off-by: Atin Mukherjee Reviewed-on: http://review.gluster.org/11488 Tested-by: Gluster Build System Tested-by: NetBSD Build System Reviewed-by: Gaurav Kumar Garg Reviewed-by: Kaushal M --- tests/bugs/glusterd/bug-1223213-peerid-fix.t | 2 ++ 1 file changed, 2 insertions(+) (limited to 'tests/bugs/glusterd/bug-1223213-peerid-fix.t') diff --git a/tests/bugs/glusterd/bug-1223213-peerid-fix.t b/tests/bugs/glusterd/bug-1223213-peerid-fix.t index 0d9829f5a79..8e7589c9c3b 100755 --- a/tests/bugs/glusterd/bug-1223213-peerid-fix.t +++ b/tests/bugs/glusterd/bug-1223213-peerid-fix.t @@ -12,7 +12,9 @@ TEST launch_cluster 2; # is > 3.5. This is to ensure 3.5 code path is hit to test that volume status # works when a node is upgraded from 3.5 to 3.7 or higher as mgmt_v3 lock is # been introduced in 3.6 version and onwards + GD1_WD=$($CLI_1 system getwd) +$CLI_1 system uuid get TEST sed -rnie "'s/(operating-version=)\w+/\130500/gip'" ${GD1_WD}/glusterd.info TEST kill_glusterd 1 -- cgit