Bug 1231197
Summary: | Snapshot daemon failed to run on newly created dist-rep volume with uss enabled | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Avra Sengupta <asengupt> | |
Component: | snapshot | Assignee: | Avra Sengupta <asengupt> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | asengupt, bugs, gluster-bugs, rjoseph, storage-qa-internal, trao | |
Target Milestone: | --- | Keywords: | Reopened | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1230635 | |||
: | 1232883 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:10:41 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: | 1230635 | |||
Bug Blocks: | 1232883 |
Comment 1
Anand Avati
2015-06-15 09:46:41 UTC
REVIEW: http://review.gluster.org/11227 (glusterd/uss/snapshot: Intialise snapdsvc after volfiles are created) posted (#2) for review on master by Avra Sengupta (asengupt) COMMIT: http://review.gluster.org/11227 committed in master by Rajesh Joseph (rjoseph) ------ commit 2b9efc920762ad93575a44ae41450f78ecdb0d9e Author: Avra Sengupta <asengupt> Date: Fri Jun 12 17:13:05 2015 +0530 glusterd/uss/snapshot: Intialise snapdsvc after volfiles are created snapd svc should be initialised only after all relevant volfiles and directories are created. Change-Id: I96770cfc0b350599cd60ff74f5ecec08145c3105 BUG: 1231197 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/11227 Reviewed-by: Atin Mukherjee <amukherj> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Rajesh Joseph <rjoseph> 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. 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 |