Bug 1336470

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: tieringAssignee: Dan Lambright <dlambrig>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.7.11CC: bugs, dlambrig, kramdoss, nbalacha, sanandpa
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.12 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1335154 Environment:
Last Closed: 2016-06-28 12:18:31 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, 1336472    
Bug Blocks: 1335973    

Comment 1 Vijay Bellur 2016-05-16 14:49:08 UTC
REVIEW: http://review.gluster.org/14361 (cluster/tier: downgrade max-cycle-time log message to INFO) posted (#1) for review on release-3.7 by Dan Lambright (dlambrig)

Comment 2 Vijay Bellur 2016-05-21 15:48:43 UTC
COMMIT: http://review.gluster.org/14361 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit 8663686c402c963d694710a5f2b11dc6a4e34354
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 14336
    
    > Change-Id: Ia7d074423019fa79443bc6ea694148b7b8da455d
    > BUG: 1335973
    > Signed-off-by: Dan Lambright <dlambrig>
    
    Change-Id: I29514c66781f49d5c36a0d3ad5dee6ab0c0368cd
    BUG: 1336470
    Signed-off-by: Dan Lambright <dlambrig>
    Reviewed-on: http://review.gluster.org/14361
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: N Balachandran <nbalacha>

Comment 3 Kaushal 2016-06-28 12:18:31 UTC
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.12, please open a new bug report.

glusterfs-3.7.12 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] https://www.gluster.org/pipermail/gluster-devel/2016-June/049918.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user