Bug 1335973

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:	mainline	CC:	bugs, dlambrig, kramdoss, sanandpa
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.9.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1335154	Environment:
Last Closed:	2017-03-27 18:24:03 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, 1336470, 1336472
Bug Blocks:

Comment 1 Vijay Bellur 2016-05-13 17:07:00 UTC

REVIEW: http://review.gluster.org/14336 (cluster/tier: downgrade max-cycle-time log message to INFO) posted (#1) for review on master by Dan Lambright (dlambrig)

Comment 2 Vijay Bellur 2016-05-16 12:24:26 UTC

COMMIT: http://review.gluster.org/14336 committed in master by Dan Lambright (dlambrig) 
------
commit 1a3e4159c8ecda51e0f7bb018e017aa0f9d522b8
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.
    
    Change-Id: Ia7d074423019fa79443bc6ea694148b7b8da455d
    BUG: 1335973
    Signed-off-by: Dan Lambright <dlambrig>
    Reviewed-on: http://review.gluster.org/14336
    Smoke: Gluster Build System <jenkins.com>
    Reviewed-by: N Balachandran <nbalacha>
    Tested-by: N Balachandran <nbalacha>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 3 Shyamsundar 2017-03-27 18:24:03 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.9.0, please open a new bug report.

glusterfs-3.9.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://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/