Bug 1737716 - Unable to create geo-rep session on a non-root setup.
Summary: Unable to create geo-rep session on a non-root setup.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
URL:
Whiteboard:
Depends On: 1734734 1734738 1739442
Blocks: 1737313 1737712
TreeView+ depends on / blocked
 
Reported: 2019-08-06 06:48 UTC by Kotresh HR
Modified: 2019-08-09 10:27 UTC (History)
8 users (show)

Fixed In Version:
Clone Of: 1734738
Environment:
Last Closed: 2019-08-06 10:59:23 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 23162 0 None Merged geo-rep: Fix mount broker setup issue 2019-08-06 10:59:22 UTC

Description Kotresh HR 2019-08-06 06:48:34 UTC 
Description of problem:
Unable to create a non-root geo-rep session on a geo-rep setup. 

Version-Release number of selected component (if applicable):
gluster-5.0

How reproducible:
Always

Steps to Reproduce:
1.Create a non-root geo-rep setup.
2.Try to create a non-root geo-rep session. 

Actual results:
# gluster volume geo-replication master-rep geoaccount.43.185::slave-rep create push-pem gluster command not found on 10.70.43.185 for user geoaccount. geo-replication command failed

Expected results:
# gluster volume geo-replication master-rep geoaccount.43.185::slave-rep
Creating geo-replication session between master-rep & geoaccount.43.185::slave-rep has been successful
Comment 1 Worker Ant 2019-08-06 07:03:44 UTC 
REVIEW: https://review.gluster.org/23162 (geo-rep: Fix mount broker setup issue) posted (#1) for review on release-5 by Kotresh HR
Comment 2 Worker Ant 2019-08-06 10:59:23 UTC 
REVIEW: https://review.gluster.org/23162 (geo-rep: Fix mount broker setup issue) merged (#1) on release-5 by Kotresh HR
Note You need to log in before you can comment on or make changes to this bug.