Bug 1422766

Summary:	Entry heal messages in glustershd.log while no entries shown in heal info
Product:	[Community] GlusterFS	Reporter:	Sunil Kumar Acharya <sheggodu>
Component:	disperse	Assignee:	Sunil Kumar Acharya <sheggodu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	aspandey, bugs, byarlaga, mzywusko, pkarampu, rhs-bugs, sheggodu
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1420619	Environment:
Last Closed:	2017-03-06 17:46:17 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:	1282731, 1420619, 1422783
Bug Blocks:

Comment 1 Worker Ant 2017-02-16 08:52:57 UTC

REVIEW: https://review.gluster.org/16635 (cluster/ec: Change log level of messages to DEBUG) posted (#1) for review on release-3.10 by Sunil Kumar Acharya (sheggodu)

Comment 2 Worker Ant 2017-02-16 08:54:23 UTC

REVIEW: https://review.gluster.org/16635 (cluster/ec: Change log level of messages to DEBUG) posted (#2) for review on release-3.10 by Sunil Kumar Acharya (sheggodu)

Comment 3 Worker Ant 2017-02-16 14:46:31 UTC

COMMIT: https://review.gluster.org/16635 committed in release-3.10 by Shyamsundar Ranganathan (srangana) 
------
commit 54848213e366d92338ad5941ab0e6081ec01f6ef
Author: Sunil Kumar Acharya <sheggodu>
Date:   Thu Feb 9 16:34:54 2017 +0530

    cluster/ec: Change log level of messages to DEBUG
    
    Heal failed or passed should not be logged as info. These can be
    observed from heal info if the heal is happening or not. If we require
    to debug a case where heal is not happening, we can set the level to
    DEBUG.
    
    >Change-Id: I062668eadd145ef809b25e818e6bca1094f54cd6
    >BUG: 1420619
    >Signed-off-by: Sunil Kumar Acharya <sheggodu>
    >Reviewed-on: https://review.gluster.org/16580
    >Smoke: Gluster Build System <jenkins.org>
    >NetBSD-regression: NetBSD Build System <jenkins.org>
    >CentOS-regression: Gluster Build System <jenkins.org>
    >Reviewed-by: Ashish Pandey <aspandey>
    
    Change-Id: I96517f9cf39340ae6883115e464b62339577fc5d
    BUG: 1422766
    Signed-off-by: Sunil Kumar Acharya <sheggodu>
    Reviewed-on: https://review.gluster.org/16635
    Reviewed-by: Xavier Hernandez <xhernandez>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.org>

Comment 4 Shyamsundar 2017-03-06 17:46:17 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.10.0, please open a new bug report.

glusterfs-3.10.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/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/