Bug 1734734 - 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 ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.5.0
Assignee: Kotresh HR
QA Contact: Kshithij Iyer
URL:
Whiteboard:
Depends On:
Blocks: 1696809 1734738 1737712 1737716 1739442
TreeView+ depends on / blocked
 
Reported: 2019-07-31 10:32 UTC by Kshithij Iyer
Modified: 2019-10-30 12:23 UTC (History)
8 users (show)

Fixed In Version: glusterfs-6.0-12
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1734738 (view as bug list)
Environment:
Last Closed: 2019-10-30 12:22:40 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:23:03 UTC

Description Kshithij Iyer 2019-07-31 10:32:36 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):
glusterfs-6.0-9

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

Additional info:

Comment 10 errata-xmlrpc 2019-10-30 12:22:40 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.

https://access.redhat.com/errata/RHEA-2019:3249


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