Bug 1244721

Summary:	glusterd: Porting left out log messages to new logging API
Product:	[Community] GlusterFS	Reporter:	Nandaja Varma <nvarma>
Component:	glusterd	Assignee:	Nandaja Varma <nvarma>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.2	CC:	amukherj, annair, bugs, gluster-bugs, kparthas, nlevinki, nsathyan, smohan, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1235991	Environment:
Last Closed:	2015-09-09 09:38:23 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:

Description Nandaja Varma 2015-07-20 11:12:20 UTC

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

Description of problem:

In glusterd, some messages are still being logged using the older logging API. This has to be ported to the new API.

Version-Release number of selected component (if applicable):
RHGS 3.1

How reproducible:

N/A

Steps to Reproduce:
N/A

Actual results:

Unavailability of new logging mechanism (MSG ID) in glusterd.

Expected results:

Implement logging based on message ids for glusterd.

--- Additional comment from Nandaja Varma on 2015-06-26 07:24:59 EDT ---

The patches in the upstream are:
master: http://review.gluster.org/11388
release-3.7: http://review.gluster.org/11422

Backport of the above patch has been sent to downstream, fixing this issue. The patch is: https://code.engineering.redhat.com/gerrit/51682

Comment 1 Anand Avati 2015-07-20 11:12:41 UTC

REVIEW: http://review.gluster.org/11719 (glusterd: Porting the left out gf_log_callingfns to new framework) posted (#1) for review on release-3.7 by Nandaja Varma (nandaja.varma)

Comment 2 Anand Avati 2015-07-23 08:44:16 UTC

REVIEW: http://review.gluster.org/11719 (glusterd: Porting the left out gf_log_callingfns to new framework.) posted (#9) for review on release-3.7 by Nandaja Varma (nandaja.varma)

Comment 3 Anand Avati 2015-07-24 05:13:41 UTC

REVIEW: http://review.gluster.org/11719 (glusterd: Porting the left out gf_log_callingfns to new framework.) posted (#10) for review on release-3.7 by Nandaja Varma (nandaja.varma)

Comment 4 Anand Avati 2015-07-28 14:11:46 UTC

REVIEW: http://review.gluster.org/11719 (glusterd: Porting the left out gf_log_callingfns to new framework.) posted (#11) for review on release-3.7 by Nandaja Varma (nandaja.varma)

Comment 5 Anand Avati 2015-07-29 02:18:46 UTC

REVIEW: http://review.gluster.org/11719 (glusterd: Porting the left out gf_log_callingfns to new framework) posted (#12) for review on release-3.7 by Nandaja Varma (nandaja.varma)

Comment 6 Anand Avati 2015-07-29 05:48:41 UTC

REVIEW: http://review.gluster.org/11719 (glusterd: Porting the left out gf_log_callingfns to new framework.) posted (#13) for review on release-3.7 by Nandaja Varma (nandaja.varma)

Comment 7 Anand Avati 2015-07-29 10:25:45 UTC

REVIEW: http://review.gluster.org/11719 (glusterd: Porting the left out gf_log_callingfns to new framework.) posted (#14) for review on release-3.7 by Nandaja Varma (nandaja.varma)

Comment 8 Kaushal 2015-09-09 09:38:23 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.4, please open a new bug report.

glusterfs-3.7.4 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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/12496
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user