Bug 1477208 - [GSS][RFE] mount.glusterfs and mount -t glusterfs should give more specific/usable error messages [NEEDINFO]
[GSS][RFE] mount.glusterfs and mount -t glusterfs should give more specific/u...
Status: NEW
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: fuse (Show other bugs)
3.2
Unspecified Linux
unspecified Severity low
: ---
: ---
Assigned To: Csaba Henk
Rahul Hinduja
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-01 09:21 EDT by Pamela Ousley
Modified: 2017-08-02 12:16 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
bkunal: needinfo? (asrivast)


Attachments (Terms of Use)

  None (edit)
Description Pamela Ousley 2017-08-01 09:21:28 EDT
Description of problem:

mount.glusterfs and mount -t glusterfs do not give specific error messages, making it difficult to troubleshoot the issue. The request is for more information to be given by default, without needing to set DEBUG level logging.

From the customer:

"It ends up with 'mount failed' on any problem. Doesn't matter if it's a firewall problem, client cannot connect node:brick port or it's just denied via auth.allow volume option. Client log messages is not telling you any usable if error level is set to ERROR. 

Connection problems (cannot connect to brick port) are visible only with DEBUG level enabled. I think that mount/connections error should be clearly logged as:

Mount failed - client not allowed in auth.allow
Mount failed - cannot connect server:port
etc..."

Please let me know if any further information is required for this RFE. Thank you.

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