Bug 1782162 - ssh-port config set is failing
Summary: ssh-port config set is failing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.5.z Batch Update 1
Assignee: Sunny Kumar
QA Contact: Sayalee
URL:
Whiteboard:
Depends On: 1692666
Blocks: 1695445
TreeView+ depends on / blocked
 
Reported: 2019-12-11 10:11 UTC by Sunny Kumar
Modified: 2020-01-30 06:43 UTC (History)
13 users (show)

Fixed In Version: glusterfs-6.0-25
Doc Type: No Doc Update
Doc Text:
Clone Of: 1692666
Environment:
Last Closed: 2020-01-30 06:42:48 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0288 0 None None None 2020-01-30 06:43:08 UTC

Description Sunny Kumar 2019-12-11 10:11:14 UTC
+++ 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

Comment 7 Mugdha Soni 2019-12-27 07:12:12 UTC
Sunny 
 
It would be really helpful if you could help with the steps to reproduce.

Comment 13 errata-xmlrpc 2020-01-30 06:42:48 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/RHBA-2020:0288


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