Bug 1611945 - [geo-rep] Cannot configure ssh_port and ssh_command options in glusterfs georeplication
Summary: [geo-rep] Cannot configure ssh_port and ssh_command options in glusterfs geor...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-03 06:47 UTC by Dimitri Ars
Modified: 2018-12-13 05:44 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-12-13 05:44:19 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Dimitri Ars 2018-08-03 06:47:31 UTC
Description of problem:
When configuring geo-replication options using the command line, this doesn't work anymore for ssh-port and ssh-command.

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

How reproducible: 100%

Steps to Reproduce:
1.Example of a working configuration option:
# gluster volume geo-replication volname ssh://1.2.3.4::certificates config ssh_options "-oPasswordAuthentication=no -oStrictHostKeyChecking=no"
geo-replication config updated successfully

Example of non-working configuration option:

# gluster volume geo-replication volname ssh://1.2.3.4::certificates config ssh_port "2222"                                                     
geo-replication config-set failed for certificates ssh://192.168.92.11::certificates
geo-replication command failed

Same for using ssh-port, ssh-command, ssh_command options and with or without quotes.

Actual results:
geo-replication command failed

Expected results:
geo-replication config updated successfully for ssh-port and ssh-command options

Additional info:
This worked fine on 3.12. I don't know if there are more options that don't work...I've tried a couple which worked fine...the ssh_port and ssh_command are ones we use.

Comment 1 Dimitri Ars 2018-08-03 06:50:37 UTC
(Oh, don't mind the 1.2.3.4 / 192.168.92.11 / volname / certificates messup in my examples :)

Comment 2 James Le Cuirot 2018-09-24 15:18:27 UTC
Same here on a brand new install.

Comment 3 Kotresh HR 2018-12-13 05:44:19 UTC
If you want to use the different ssh-port for geo-rep. It has to be specified during creation itself.

gluster volume geo-replication <MASTER_VOL> <SLAVE_HOST>::<SLAVE_VOL> create [[ssh-port n][[no-verify]|[push-pem]]] [force]

If the session is already created, please follow below steps.

1. Stop geo-rep
2. gluster volume geo-replication <MASTER_VOL> <SLAVE_HOST>::<SLAVE_VOL> create ssh-port <n> push-pem force
3. Start geo-rep

I am closing the bug. Please re-open if the above does not work.


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