[Bugs] [Bug 1258406] New: libgfapi : pending - porting log messages to a new framework
bugzilla at redhat.com
bugzilla at redhat.com
Mon Aug 31 10:02:48 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1258406
Bug ID: 1258406
Summary: libgfapi : pending - porting log messages to a new
framework
Product: GlusterFS
Version: 3.7.3
Component: logging
Severity: medium
Assignee: bugs at gluster.org
Reporter: mselvaga at redhat.com
CC: annair at redhat.com, bugs at gluster.org,
gluster-bugs at redhat.com, mselvaga at redhat.com,
sasundar at redhat.com
Depends On: 1242268
Blocks: 1241957, 1252807
+++ This bug was initially created as a clone of Bug #1242268 +++
Description of problem:
------------------------
There are few gf_log instance under api directory in the source code base of
glusterfs. These should be ported to new logging framework
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHGS 3.1 Nightly Build ( glusterfs-3.7.1-8.el6rhs )
Instances of gf_log
-------------------
[satheesaran at dhcppc1 api]$ grep -r "gf_log " * -A1
src/glfs-fops.c: gf_log (THIS->name, GF_LOG_DEBUG,
src/glfs-fops.c- "Upcall gfapi callback is called");
--
src/glfs-fops.c: gf_log (THIS->name, GF_LOG_TRACE, "Upcall gfapi gfid =
%s"
src/glfs-fops.c- "ret = %d", (char *)(upcall_data->gfid), ret);
--
src/glfs-fops.c: gf_log (THIS->name, GF_LOG_ERROR, "Upcall entry
allocation"
src/glfs-fops.c- "failed.");
--
src/glfs-handleops.c: gf_log (subvol->name,
GF_LOG_WARNING,
src/glfs-handleops.c- "handle creation of %s
failed: %s",
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1241957
[Bug 1241957] [ TRACKER ] : Tracker for porting pending log messages
porting to new framework
https://bugzilla.redhat.com/show_bug.cgi?id=1242268
[Bug 1242268] libgfapi : pending - porting log messages to a new framework
https://bugzilla.redhat.com/show_bug.cgi?id=1252807
[Bug 1252807] libgfapi : pending - porting log messages to a new framework
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list