+++ This bug was initially created as a clone of Bug #1792276 +++ Description of problem: If non-standard ssh-port is used, Geo-rep can be configured to use ssh port by using config option, the value should be in allowed port range and non negative. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: $ gluster volume geo-replication master 127.0.0.1::slave config ssh-port -22 geo-replication config updated successfully $ gluster volume geo-replication master 127.0.0.1::slave config ssh-port 22222222 geo-replication config updated successfully --- Additional comment from Worker Ant on 2020-01-17 13:14:06 UTC --- REVIEW: https://review.gluster.org/24035 (geo-rep: Fix ssh-port validation) posted (#1) for review on master by Sunny Kumar --- Additional comment from Worker Ant on 2020-01-19 06:32:07 UTC --- REVIEW: https://review.gluster.org/24035 (geo-rep: Fix ssh-port validation) merged (#2) on master by Sunny Kumar
Upstream patch: https://review.gluster.org/#/c/glusterfs/+/24035/
(In reply to Sunny Kumar from comment #1) > Upstream patch: > https://review.gluster.org/#/c/glusterfs/+/24035/ This is merged. What's the next step? Why is it stuck on POST?
This should be a two liner automated script. Is it automated already?
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 (glusterfs bug fix and enhancement update), 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/RHBA-2020:5603