+++ 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@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",
REVIEW: http://review.gluster.org/11891 (libgfapi : port missing gf_log's to gf_msg) posted (#2) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11891 (libgfapi : port missing gf_log's to gf_msg) posted (#3) for review on master by Manikandan Selvaganesh (mselvaga)
COMMIT: http://review.gluster.org/11891 committed in master by Raghavendra G (rgowdapp) ------ commit 1e0644031c7ac0fa28f0912e951a9238f7bbe8ab Author: Manikandan Selvaganesh <mselvaga> Date: Wed Aug 12 14:46:29 2015 +0530 libgfapi : port missing gf_log's to gf_msg Change-Id: I0c5320c09b4a5ff1e9df61a86ac7bd47c1bb1bbb BUG: 1252807 Signed-off-by: Manikandan Selvaganesh <mselvaga> Reviewed-on: http://review.gluster.org/11891 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Raghavendra Talur <rtalur> Reviewed-by: jiffin tony Thottan <jthottan> Reviewed-by: Humble Devassy Chirammal <humble.devassy> Reviewed-by: Raghavendra G <rgowdapp>
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user