Bug 1257149

Summary:	Provide more meaningful errors on peer probe and peer detach
Product:	[Community] GlusterFS	Reporter:	Brad Hubbard <bhubbard>
Component:	glusterd	Assignee:	Brad Hubbard <bhubbard>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1257394 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:33:45 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:	1257394

Description Brad Hubbard 2015-08-26 11:20:33 UTC

Description of problem:

When a peer probe or peer detach fails glusterd currently reports "peer probe: failed: Probe returned with unknown errno 107". The process should be able to provide more information than that.

Comment 1 Brad Hubbard 2015-08-27 02:03:17 UTC

http://review.gluster.org/#/c/12021/

Comment 2 Anand Avati 2015-08-27 02:16:17 UTC

REVIEW: http://review.gluster.org/12021 (glusterd: Return better error messages for probe and detach failures) posted (#2) for review on master by Brad Hubbard (bhubbard)

Comment 3 Anand Avati 2015-08-31 01:25:29 UTC

REVIEW: http://review.gluster.org/12021 (glusterd: Return better error messages for probe and detach failures) posted (#3) for review on master by Brad Hubbard (bhubbard)

Comment 4 Anand Avati 2015-08-31 01:25:38 UTC

REVIEW: http://review.gluster.org/12049 (fix testcase that depends on peer probe error output) posted (#1) for review on master by Brad Hubbard (bhubbard)

Comment 5 Anand Avati 2015-08-31 08:49:23 UTC

REVIEW: http://review.gluster.org/12021 (glusterd: Return better error messages for probe and detach failures) posted (#4) for review on master by Brad Hubbard (bhubbard)

Comment 6 Niels de Vos 2016-06-16 13:33:45 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.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