Bug 1473587 – [3.6][glusterfs] Improve error messaging for failed volume mount

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1473587 - [3.6][glusterfs] Improve error messaging for failed volume mount

Summary:	[3.6][glusterfs] Improve error messaging for failed volume mount

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Storage (Show other bugs)
Sub Component:
Version:	3.6.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	3.6.z
Assigned To:	Jan Safranek
QA Contact:	Jianwei Hou
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression

Depends On:	1466249
Blocks:
	Show dependency tree / graph

Reported:	2017-07-21 04:29 EDT by Jan Safranek
Modified:	2017-08-10 01:32 EDT (History)
CC List:	9 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1466249
Environment:
Last Closed:	2017-08-10 01:32:16 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2017:1716	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.6 RPM Release Advisory	2017-08-10 05:02:50 EDT

Groups: None (edit)

Comment 1 Jan Safranek 2017-07-21 04:30:30 EDT

Trying to catch 3.6.0...

Comment 2 Jan Safranek 2017-07-21 06:23:40 EDT

Created https://github.com/openshift/origin/pull/15396

Comment 4 Jianwei Hou 2017-07-31 03:36:06 EDT

Verified on v3.6.172.0.1

When an invalid ip is given, the error message could clearly describe the fail reason.
FailedMount	MountVolume.SetUp failed for volume "kubernetes.io/glusterfs/61116d33-75c0-11e7-946e-0050569f1b82-gluster" (spec.Name: "gluster") pod "61116d33-75c0-11e7-946e-0050569f1b82" (UID: "61116d33-75c0-11e7-946e-0050569f1b82") with: glusterfs: mount failed: exit status 1 the following error information was pulled from the glusterfs log to help diagnose this issue: 
[2017-07-31 07:26:28.019612] E [socket.c:2395:socket_connect_finish] 0-glusterfs: connection to 11.11.11.118:24007 failed (Connection timed out)
[2017-07-31 07:26:28.019835] E [glusterfsd-mgmt.c:1907:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: 11.11.11.118 (Transport endpoint is not connected)

Comment 6 errata-xmlrpc 2017-08-10 01:32:16 EDT

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://access.redhat.com/errata/RHEA-2017:1716

Note You need to log in before you can comment on or make changes to this bug.