Bug 1445590

Summary:	Incorrect and redundant logs in the DHT rmdir code path
Product:	[Community] GlusterFS	Reporter:	Nithya Balachandran <nbalacha>
Component:	distribute	Assignee:	Nithya Balachandran <nbalacha>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.11.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1446227 (view as bug list)		Environment:
Last Closed:	2017-05-30 18:51:22 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:
Bug Depends On:
Bug Blocks:	1445195, 1446227, 1447186

Description Nithya Balachandran 2017-04-26 04:31:07 UTC

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:

Comment 1 Worker Ant 2017-04-26 04:56:58 UTC

REVIEW: https://review.gluster.org/17118 (cluster/dht Remove redundant logs in dht rmdir) posted (#1) for review on master by N Balachandran (nbalacha)

Comment 2 Worker Ant 2017-04-26 09:44:09 UTC

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>

Comment 3 Shyamsundar 2017-05-30 18:51:22 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.11.0, please open a new bug report.

glusterfs-3.11.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://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/