Bug 1722740 - [GSS] geo-replication sessions going faulty
Summary: [GSS] geo-replication sessions going faulty
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Sunny Kumar
QA Contact:
URL:
Whiteboard:
Depends On: 1712591
Blocks: 1696809 1764007 1764172
TreeView+ depends on / blocked
 
Reported: 2019-06-21 06:57 UTC by Sunny Kumar
Modified: 2019-10-22 12:25 UTC (History)
2 users (show)

Fixed In Version:
Clone Of: 1712591
: 1764007 1764172 (view as bug list)
Environment:
Last Closed: 2019-06-28 09:37:55 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22920 0 None Merged geo-rep : fix gluster command path for non-root session 2019-06-28 09:37:54 UTC

Description Sunny Kumar 2019-06-21 06:57:03 UTC 
Description of problem:

 gluster command not found.

How reproducible:

Always

Steps to Reproduce:
1. Setup non-root geo-replication
2. Start geo-replication
2. Session goes to faulty


Expected results:

Session should not go faulty
Comment 1 Sunny Kumar 2019-06-21 07:02:29 UTC 
Problem:
    gluster command not found.
    
Cause:
    In Volinfo class we issue command 'gluster vol info' to perform
    operation like getting brick_root etc.
    When geo-rep session is configured for non-root user Volinfo class
    fails to issue gluster command due to unavailability of gluster
    binary path for non-root user.
    
Solution:
    Use config value 'slave-gluster-command-dir' to get path for gluster
    binaries.
Comment 2 Sunny Kumar 2019-06-21 07:20:05 UTC 
Upstream Patch:

https://review.gluster.org/#/c/glusterfs/+/22920/
Comment 3 Worker Ant 2019-06-28 09:37:55 UTC 
REVIEW: https://review.gluster.org/22920 (geo-rep : fix gluster command path for non-root session) merged (#6) on master by Kotresh HR
Note You need to log in before you can comment on or make changes to this bug.