Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1359607

Summary: [RFE] Non root Geo-replication Error logs improvements
Product: Red Hat Gluster Storage Reporter: Aravinda VK <avishwan>
Component: geo-replicationAssignee: Kotresh HR <khiremat>
Status: CLOSED ERRATA QA Contact: Rahul Hinduja <rhinduja>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: amukherj, bugs, csaba, khiremat, rcyriac, rhinduja, rhs-bugs, rreddy
Target Milestone: ---Keywords: FutureFeature
Target Release: RHGS 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: glusterfs-3.8.4-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1346138 Environment:
Last Closed: 2017-03-23 05:40:10 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:
Bug Depends On: 1346138, 1370995    
Bug Blocks: 1351503    

Description Aravinda VK 2016-07-25 06:43:20 UTC
+++ This bug was initially created as a clone of Bug #1346138 +++

Description of problem:
During Non-root Geo-replication setup, if Mountbroker mount fails Gluster just shows Permission denied or Operation not Permitted errors. 

Log/stderr need to be enhanced to show exact reason for Mount failures. (User dir permissions, Arguments mismatch, Invalid Log file path etc)

Comment 3 Kotresh HR 2016-08-25 16:56:40 UTC
Upstream Patch:

Comment 4 Kotresh HR 2016-09-15 14:10:24 UTC
Upstream patchs:

Comment 6 Atin Mukherjee 2016-09-15 14:38:08 UTC
downstream patches are merged.

Comment 9 Rahul Hinduja 2017-02-06 11:58:59 UTC
Verified with the build: glusterfs-geo-replication-3.8.4-13.el7rhgs.x86_64

Carried the test scenario's by manually injecting the errors in the glusterd vol file to simulate the errors. Following errors were correctly reported:

[2017-02-06 11:38:40.455740] I [MSGID: 106496] [glusterd-handler.c:3182:__glusterd_handle_mount] 0-glusterd: Received mount req
[2017-02-06 11:38:40.455852] E [MSGID: 106062] [glusterd-mountbroker.c:548:glusterd_do_mount] 0-management: 'option mountbroker-root' missing in glusterd vol file
[2017-02-06 11:38:40.455854] W [MSGID: 106176] [glusterd-mountbroker.c:724:glusterd_do_mount] 0-management: unsuccessful mount request [No such file or directory]

[2017-02-06 11:41:06.526083] I [MSGID: 106496] [glusterd-handler.c:3182:__glusterd_handle_mount] 0-glusterd: Received mount req
[2017-02-06 11:41:06.526148] E [MSGID: 106581] [glusterd-mountbroker.c:579:glusterd_do_mount] 0-management: Missing mspec: Check the corresponding option in glusterd vol file for mountbroker user: geoaccount [No such file or directory]
[2017-02-06 11:41:06.526173] W [MSGID: 106176] [glusterd-mountbroker.c:724:glusterd_do_mount] 0-management: unsuccessful mount request [No such file or directory]

[2017-02-06 11:51:42.122744] I [MSGID: 106496] [glusterd-handler.c:3182:__glusterd_handle_mount] 0-glusterd: Received mount req
[2017-02-06 11:51:42.123411] E [MSGID: 106176] [glusterd-mountbroker.c:598:glusterd_do_mount] 0-management: Either volume is not started or volinfo not found [No such file or directory]
[2017-02-06 11:51:42.123524] W [MSGID: 106176] [glusterd-mountbroker.c:724:glusterd_do_mount] 0-management: unsuccessful mount request [No such file or directory]

[2017-02-06 11:55:51.700182] E [MSGID: 106582] [glusterd-mountbroker.c:484:evaluate_mount_request] 0-management: Mountbroker spec mismatch!!! SET: 2 COMPONENT: 0. Review the mount args passed [Operation not permitted]
[2017-02-06 11:55:51.700278] W [MSGID: 106176] [glusterd-mountbroker.c:724:glusterd_do_mount] 0-management: unsuccessful mount request [Operation not permitted]

Moving this bug to verified state. Any new error required will be raised and tracked separately

Comment 11 errata-xmlrpc 2017-03-23 05:40:10 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.