Bug 1246946

Summary:	critical message seen in glusterd log file, when detaching a peer, but no functional loss
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED ERRATA	QA Contact:	Byreddy <bsrirama>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, asrivast, bsrirama, divya, nlevinki, vagarwal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.1
Hardware:	x86_64
OS:	Linux
Whiteboard:	glusterd
Fixed In Version:	glusterfs-3.7.1-12	Doc Type:	Bug Fix
Doc Text:	Previously, while detaching a peer from a node, the glusterd service was logging a critical message saying that it could not find the peer. With this fix, the glusterd service does not log this error.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-05 07:21:15 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:	1212437, 1252680
Bug Blocks:	1251815

Description SATHEESARAN 2015-07-27 02:12:32 UTC

Description of problem:
------------------------
While detaching a peer from host1, critical error message is seen in glusterd logs in same host. Functionally wasn't affected but these critical error messages should not be seen in glusterd logs

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHGS 3.1 

How reproducible:
------------------
Always

Steps to Reproduce:
-------------------
1. Detach a peer from the cluster
2. Observe glusterd logs

Actual results:
---------------
Critical message was seen in glusterd logs as follows :

"[2015-07-26 09:10:29.584438] C [MSGID: 106129] [glusterd-handler.c:5019:__glusterd_peer_rpc_notify] 0-management: Could not find peer dhcp37-58.lab.eng.blr.redhat.com(00000000-0000-0000-0000-000000000000) [No such file or directory]"

Expected results:
------------------
There shouldn't be any critical messages

Comment 1 Atin Mukherjee 2015-07-27 03:56:33 UTC

An upstream patch http://review.gluster.org/#/c/10272/ is been already posted for this.

Comment 3 Atin Mukherjee 2015-08-13 07:05:55 UTC

Downstream patch : https://code.engineering.redhat.com/gerrit/55047

Comment 5 Byreddy 2015-08-24 10:48:03 UTC

Version used to Verify this bug is glusterfs-3.7.1-12.
No more we are seeing this issue, Moving this bug to Verified state.

Comment 6 SATHEESARAN 2015-09-22 12:06:54 UTC

Atin,

I see the doc_text is explaining lots of technical information.
It could be concise explaining the actual problem

Comment 7 Atin Mukherjee 2015-09-23 04:04:08 UTC

(In reply to SATHEESARAN from comment #6)
> Atin,
> 
> I see the doc_text is explaining lots of technical information.
> It could be concise explaining the actual problem

Its just that we should remove the log instance here, apart from that I don't think other stuffs are technical.

Divya,

Could you reword the doc text as :
"Previously, while detaching a peer from a node, glusterd service was logging a critical message saying could not find the peer. With this fix, glusterd service doesn't log this error."

Comment 8 SATHEESARAN 2015-09-23 05:18:40 UTC

(In reply to Atin Mukherjee from comment #7)
> (In reply to SATHEESARAN from comment #6)
> > Atin,
> > 
> > I see the doc_text is explaining lots of technical information.
> > It could be concise explaining the actual problem
> 
> Its just that we should remove the log instance here, apart from that I
> don't think other stuffs are technical.
> 
> Divya,
> 
> Could you reword the doc text as :
> "Previously, while detaching a peer from a node, glusterd service was
> logging a critical message saying could not find the peer. With this fix,
> glusterd service doesn't log this error."

Thanks Atin and that looks simple and understandable for admin/user

Comment 9 Divya 2015-09-23 06:17:35 UTC

Updated the doc text based on Comment 7.

Comment 10 Atin Mukherjee 2015-09-23 07:23:02 UTC

Doc text signed off

Comment 12 errata-xmlrpc 2015-10-05 07:21:15 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-1845.html