+++ This bug was initially created as a clone of Bug #1692666 +++ Description of problem: If non-standard ssh-port is used, Geo-rep can be configured to use that ssh port by configuring as below ``` gluster volume geo-replication <mastervol> <slavehost>::<slavevol> config ssh-port 2222 ``` But this command is failing even if a valid value is passed. ``` $ gluster v geo gv1 centos.sonne::gv2 config ssh-port 2222 geo-replication config-set failed for gv1 centos.sonne::gv2 geo-replication command failed ``` --- Additional comment from Worker Ant on 2019-03-26 08:00:05 UTC --- REVIEW: https://review.gluster.org/22418 (geo-rep: fix integer config validation) posted (#1) for review on master by Aravinda VK --- Additional comment from Worker Ant on 2019-03-27 14:35:10 UTC --- REVIEW: https://review.gluster.org/22418 (geo-rep: fix integer config validation) merged (#2) on master by Amar Tumballi
REVIEW: https://review.gluster.org/22489 (geo-rep: fix integer config validation) posted (#1) for review on release-6 by Aravinda VK
REVIEW: https://review.gluster.org/22489 (geo-rep: fix integer config validation) merged (#3) on release-6 by Shyamsundar Ranganathan
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-6.1, please open a new bug report. glusterfs-6.1 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-April/000124.html [2] https://www.gluster.org/pipermail/gluster-users/