Bug 1336472
| Summary: | [Tiering]: The message 'Max cycle time reached..exiting migration' incorrectly displayed as an 'error' in the logs | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Dan Lambright <dlambrig> |
| Component: | tiering | Assignee: | Dan Lambright <dlambrig> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | bugs <bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.8.0 | CC: | bugs, dlambrig, kramdoss, nbalacha, sanandpa |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1335154 | Environment: | |
| Last Closed: | 2016-06-16 14:06: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: | 1335154 | ||
| Bug Blocks: | 1335973, 1336470 | ||
|
Comment 1
Vijay Bellur
2016-05-16 14:52:06 UTC
COMMIT: http://review.gluster.org/14362 committed in release-3.8 by Dan Lambright (dlambrig) ------ commit 69fccb84bc2d84bb3b3fce32836e1aea805605a9 Author: Dan Lambright <dlambrig> Date: Fri May 13 13:06:21 2016 -0400 cluster/tier: downgrade max-cycle-time log message to INFO The "max cycle time" log message was incorrectly logged as an error. Downgrade it to INFO. This is a backport of 14361 > Change-Id: Ia7d074423019fa79443bc6ea694148b7b8da455d > BUG: 1335973 > Signed-off-by: Dan Lambright <dlambrig> Change-Id: I91cbd0165fa6c72d3fa5e373bc12578ef0bde9da BUG: 1336472 Signed-off-by: Dan Lambright <dlambrig> Reviewed-on: http://review.gluster.org/14362 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Smoke: Gluster Build System <jenkins.com> Reviewed-by: N Balachandran <nbalacha> 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 |