Gluster users - Feb 2017 - geo-replication ssh-port not working as expected...

Hello all,

currently i'm trying to setup a geo-replication between two dist.-repl. 
4 node-gluster on a different port than 22.
we are running 3.7.18 on ubuntu 16.04...
in regard to the docs the ssh-port can be configured by :

root at gl-master-01:/var/lib/glusterd/geo-replication# gluster volume 
geo-replication mvol1 gl-slave-01-int::svol1 create ssh-port 2503 push-pem
Creating geo-replication session between mvol1 & gl-slave-01-int::svol1 
has been successful
root at gl-master-01:/var/lib/glusterd/geo-replication#

This is what i can see on slave side when creating the session... :

root at gl-slave-01:/var/log/glusterfs# tail -f cmd_history.log
...
[2017-02-20 12:18:03.043860]  : system:: copy file 
/geo-replication/mvol1_svol1_common_secret.pem.pub : SUCCESS
[2017-02-20 12:18:03.409927]  : system:: execute add_secret_pub root 
geo-replication/mvol1_svol1_common_secret.pem.pub : SUCCESS

But directly after starting the geo-replication this error occurs in the 
ssh...log on the master...looks like the standard port 22 is still used 
for the geo-replication :

[2017-02-20 12:30:24.148097] E 
[syncdutils(/brick1/mvol1):252:log_raise_exception] <top>: connection to 
peer is broken
[2017-02-20 12:30:24.148766] E [resource(/brick1/mvol1):234:errlog] 
Popen: command "ssh -oPasswordAuthentication=no 
-oStrictHostKeyChecking=no -i 
/var/lib/glusterd/geo-replication/secret.pem -p 22 -oControlMaster=auto 
-S /tmp/gsyncd-aux-ssh-X80vSd/db73a3bfe7357366aff777392fc60a7e.sock 
root at gl-slave-01-int /nonexistent/gsyncd --session-owner 
f05cfb68-7a92-434d-83cc-1347d43af5e8 -N --listen --timeout 120 
gluster://localhost:svol1" returned with 255, saying:
[2017-02-20 12:30:24.149255] E [resource(/brick1/mvol1):238:logerr] 
Popen: ssh> ssh: connect to host gl-slave-01-int port 22: Connection refused

In 3.4 (and i believe in 3.5 and 3.6) we were able to configure the port 
directly in the 
/var/lib/glusterd/geo-replication/<session-name>/gsyncd.conf by adding 
for example '-p 2503' :

ssh_command_tar = ssh -oPasswordAuthentication=no 
-oStrictHostKeyChecking=no -i 
/var/lib/glusterd/geo-replication/tar_ssh.pem -p 2503
ssh_command = ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no 
-i /var/lib/glusterd/geo-replication/secret.pem -p 2503

Doing so in all 'gsyncd.conf' on all master-nodes does not lead to 
success....:

[2017-02-20 12:41:06.400605] E 
[syncdutils(/brick1/mvol1):252:log_raise_exception] <top>: connection to 
peer is broken
[2017-02-20 12:41:06.400985] E [resource(/brick1/mvol1):234:errlog] 
Popen: command "ssh -oPasswordAuthentication=no 
-oStrictHostKeyChecking=no -i 
/var/lib/glusterd/geo-replication/secret.pem -p 2503 -p 22 
-oControlMaster=auto -S 
/tmp/gsyncd-aux-ssh-XQf2hg/db73a3bfe7357366aff777392fc60a7e.sock 
root at gl-slave-01-int /nonexistent/gsyncd --session-owner 
f05cfb68-7a92-434d-83cc-1347d43af5e8 -N --listen --timeout 120 
gluster://localhost:svol1" returned with 255, saying:
[2017-02-20 12:41:06.401189] E [resource(/brick1/mvol1):238:logerr] 
Popen: ssh> ssh: connect to host gl-slave-01-int port 22: Connection refused

Somehow it looks like port 22 is hard coded...
Does anybody know how to successfully change the ssh port for a 
geo-replication session...?

any hint would be appreciated...

best regards
dietmar
-- 

Dietmar Putz
3Q GmbH
Wetzlarer Str. 86
D-14482 Potsdam
  
Telefax:  +49 (0)331 / 2797 866 - 1
Telefon:  +49 (0)331 / 2797 866 - 8
Mobile:   +49 171 / 90 160 39
Mail:     dietmar.putz at 3qsdn.com