+++ This bug was initially created as a clone of Bug #1445590 +++ Description of problem: Incorrect and redundant logs were introduced as a part of https://review.gluster.org/#/c/17065/ Version-Release number of selected component (if applicable): How reproducible: Consistently. Steps to Reproduce: 1. Perform the test steps given in https://bugzilla.redhat.com/show_bug.cgi?id=1442724 2. Check the mount logs 3. Actual results: Log flooded with I [dht-common.c:8263:dht_rmdir_lookup_cbk] 0-dht: dht_rmdir_lookup_cbk <dirname> Expected results: No log flooding. Additional info: --- Additional comment from Worker Ant on 2017-04-26 00:56:58 EDT --- REVIEW: https://review.gluster.org/17118 (cluster/dht Remove redundant logs in dht rmdir) posted (#1) for review on master by N Balachandran (nbalacha) --- Additional comment from Worker Ant on 2017-04-26 05:44:09 EDT --- COMMIT: https://review.gluster.org/17118 committed in master by Raghavendra G (rgowdapp) ------ commit 25f0a7b153b30b2c0e8278b0ce11d1199c3fb006 Author: N Balachandran <nbalacha> Date: Wed Apr 26 10:24:40 2017 +0530 cluster/dht Remove redundant logs in dht rmdir Removing redundant logs were introduced in https://review.gluster.org/#/c/17065/ Change-Id: I0d6055488b51a13c91d2121e87f653cdb94888b0 BUG: 1445590 Signed-off-by: N Balachandran <nbalacha> Reviewed-on: https://review.gluster.org/17118 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Susant Palai <spalai> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp>
REVIEW: https://review.gluster.org/17130 (cluster/dht Remove redundant logs in dht rmdir) posted (#1) for review on release-3.10 by N Balachandran (nbalacha)
COMMIT: https://review.gluster.org/17130 committed in release-3.10 by Shyamsundar Ranganathan (srangana) ------ commit 5888e2f7f3e3cea0cd02059c5548743185998e86 Author: N Balachandran <nbalacha> Date: Wed Apr 26 10:24:40 2017 +0530 cluster/dht Remove redundant logs in dht rmdir Removing redundant logs were introduced in https://review.gluster.org/#/c/17065/ > BUG: 1445590 > Signed-off-by: N Balachandran <nbalacha> > Reviewed-on: https://review.gluster.org/17118 > Smoke: Gluster Build System <jenkins.org> > NetBSD-regression: NetBSD Build System <jenkins.org> > Reviewed-by: Susant Palai <spalai> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Raghavendra G <rgowdapp> (cherry picked from commit 25f0a7b153b30b2c0e8278b0ce11d1199c3fb006) Change-Id: I0d6055488b51a13c91d2121e87f653cdb94888b0 BUG: 1446227 Signed-off-by: N Balachandran <nbalacha> Reviewed-on: https://review.gluster.org/17130 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Shyamsundar Ranganathan <srangana>
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.2, please open a new bug report.