Bug 1671217

Summary:	core: move "dict is NULL" logs to DEBUG log level
Product:	[Community] GlusterFS	Reporter:	Milind Changire <mchangir>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1671213	Environment:
Last Closed:	2019-02-04 14:47:44 UTC	Type:	---
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:	1671213, 1693201
Bug Blocks:

Description Milind Changire 2019-01-31 06:04:55 UTC

+++ This bug was initially created as a clone of Bug #1671213 +++

Description of problem:
too many "dict is NULL" get printed if dict_ref() and dict_unref() are passed a NULL pointer

--- Additional comment from Worker Ant on 2019-01-31 11:32:34 IST ---

REVIEW: https://review.gluster.org/22128 (core: move \"dict is NULL\" logs to DEBUG log level) posted (#1) for review on master by Milind Changire

Comment 1 Worker Ant 2019-01-31 06:06:00 UTC

REVIEW: https://review.gluster.org/22129 (core: move \"dict is NULL\" logs to DEBUG log level) posted (#1) for review on release-5 by Milind Changire

Comment 2 Worker Ant 2019-02-04 14:47:44 UTC

REVIEW: https://review.gluster.org/22129 (core: move \"dict is NULL\" logs to DEBUG log level) merged (#2) on release-5 by Shyamsundar Ranganathan

Comment 3 Shyamsundar 2019-03-27 13:44:02 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-5.5, please open a new bug report.

glusterfs-5.5 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://lists.gluster.org/pipermail/announce/2019-March/000119.html
[2] https://www.gluster.org/pipermail/gluster-users/