Bug 1473587
| Summary: | [3.6][glusterfs] Improve error messaging for failed volume mount | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jan Safranek <jsafrane> |
| Component: | Storage | Assignee: | Jan Safranek <jsafrane> |
| Status: | CLOSED ERRATA | QA Contact: | Jianwei Hou <jhou> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.6.0 | CC: | aos-bugs, aos-storage-staff, bchilds, hchiramm, jhou, jsafrane, mchangir, rhs-bugs, smunilla |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 3.6.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1466249 | Environment: | |
| Last Closed: | 2017-08-10 05:32:16 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: | 1466249 | ||
| Bug Blocks: | |||
|
Comment 1
Jan Safranek
2017-07-21 08:30:30 UTC
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) 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 |