[Bugs] [Bug 1213295] Glusterd crashed after updating to 3.8 nightly build
bugzilla at redhat.com
bugzilla at redhat.com
Mon Apr 27 04:55:03 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1213295
--- Comment #7 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10304 committed in master by Kaushal M
(kaushal at redhat.com)
------
commit 18fd2fdd60839d737ab0ac64f33a444b54bdeee4
Author: Atin Mukherjee <amukherj at redhat.com>
Date: Mon Apr 20 17:37:21 2015 +0530
glusterd: initialize snapd svc at volume restore path
In restore path snapd svc was not initialized because of which any glusterd
instance which went down and came back may have uninitialized snapd svc.
The
reason I used 'may' is because depending on the nodes in the cluster. In a
single node cluster this wouldn't be a problem since glusterd_spawn_daemon
takes
care of initializing it.
Change-Id: I2da1e419a0506d3b2742c1cf39a3b9416eb3c305
BUG: 1213295
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-on: http://review.gluster.org/10304
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Tested-by: NetBSD Build System
Reviewed-by: Kaushal M <kaushal at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ByKnxzsmHr&a=cc_unsubscribe
More information about the Bugs
mailing list