[Bugs] [Bug 1764007] New: geo-replication sessions going faulty

bugzilla at redhat.com bugzilla at redhat.com
Tue Oct 22 07:13:15 UTC 2019


https://bugzilla.redhat.com/show_bug.cgi?id=1764007

            Bug ID: 1764007
           Summary: geo-replication sessions going faulty
           Product: GlusterFS
           Version: 7
          Hardware: x86_64
                OS: Linux
            Status: NEW
         Component: geo-replication
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: bugs at gluster.org, sunkumar at redhat.com
        Depends On: 1712591, 1722740
            Blocks: 1696809
  Target Milestone: ---
    Classification: Community



+++ This bug was initially created as a clone of Bug #1722740 +++

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

--- Additional comment from Sunny Kumar on 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.

--- Additional comment from Sunny Kumar on 2019-06-21 07:20:05 UTC ---

Upstream Patch:

https://review.gluster.org/#/c/glusterfs/+/22920/

--- Additional comment from Worker Ant on 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


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1722740
[Bug 1722740] [GSS] geo-replication sessions going faulty
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list