Bug 1233518
Summary: | [Backup]: Glusterfind session(s) created before starting the volume results in 'changelog not available' error, eventually | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Kotresh HR <khiremat> |
Component: | glusterfind | Assignee: | Kotresh HR <khiremat> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.7.0 | CC: | avishwan, bugs, khiremat, mchangir, sanandpa |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1232729 | Environment: | |
Last Closed: | 2015-07-30 09:51:58 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: | 1228598, 1232729 | ||
Bug Blocks: | 1223636 |
Description
Kotresh HR
2015-06-19 05:38:01 UTC
REVIEW: http://review.gluster.org/11322 (tools/glusterfind: Fail glusterfind creation if volume is offline) posted (#1) for review on release-3.7 by Kotresh HR (khiremat) REVIEW: http://review.gluster.org/11322 (tools/glusterfind: Fail glusterfind creation if volume is offline) posted (#2) for review on release-3.7 by Kotresh HR (khiremat) COMMIT: http://review.gluster.org/11322 committed in release-3.7 by Venky Shankar (vshankar) ------ commit 0f6e81313048fb2be9b25765a45c612912fea123 Author: Kotresh HR <khiremat> Date: Wed Jun 17 17:05:22 2015 +0530 tools/glusterfind: Fail glusterfind creation if volume is offline Following two fixes are done. 1. Fail glusterfind session creation if volume is not online even before session directories are created. This avoids 'glusterfind list' to pick the session directories and show status as 'Session Corrupted'. 2. Check of '!Started' instead of wether the volume is 'Stopped'. It covers all the cases. BUG: 1233518 Change-Id: Ie01a87500578b9cc3eb72aabd0f24f632fbee58f Reviewed-on: http://review.gluster.org/11278 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/11322 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Aravinda VK <avishwan> 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.7.3, please open a new bug report. glusterfs-3.7.3 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12078 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |