Bug 1673972

Summary:	insufficient logging in glusterd_resolve_all_bricks
Product:	[Community] GlusterFS	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-11 16:25:14 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:	1672818, 1732875

Description Atin Mukherjee 2019-02-08 15:54:00 UTC

Description of problem:

In case, during glusterd restart in case host resolution fails, it's difficult to identify for which brick and the volume the resolution has failed. Until and unless glusterd is run in debug mode the sufficient logs can't be captured. This bug is to track this missing information in the log.

Version-Release number of selected component (if applicable):
release-6

Comment 1 Worker Ant 2019-02-08 16:05:41 UTC

REVIEW: https://review.gluster.org/22181 (glusterd: improve logging) posted (#1) for review on release-6 by Atin Mukherjee

Comment 2 Worker Ant 2019-02-11 16:25:14 UTC

REVIEW: https://review.gluster.org/22181 (glusterd: improve logging) merged (#2) on release-6 by Shyamsundar Ranganathan

Comment 3 Shyamsundar 2019-03-25 16:33:15 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-6.0, please open a new bug report.

glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/