[Bugs] [Bug 1782162] New: ssh-port config set is failing

bugzilla at redhat.com bugzilla at redhat.com
Wed Dec 11 10:11:14 UTC 2019


https://bugzilla.redhat.com/show_bug.cgi?id=1782162

            Bug ID: 1782162
           Summary: ssh-port config set is failing
           Product: Red Hat Gluster Storage
           Version: rhgs-3.5
            Status: NEW
         Component: geo-replication
          Severity: high
          Assignee: sunkumar at redhat.com
          Reporter: sunkumar at redhat.com
        QA Contact: rhinduja at redhat.com
                CC: avishwan at redhat.com, bugs at gluster.org,
                    csaba at redhat.com, khiremat at redhat.com,
                    rhs-bugs at redhat.com, sabose at redhat.com,
                    storage-qa-internal at redhat.com
        Depends On: 1692666
            Blocks: 1695445
  Target Milestone: ---
    Classification: Red Hat



+++ 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


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1692666
[Bug 1692666] ssh-port config set is failing
https://bugzilla.redhat.com/show_bug.cgi?id=1695445
[Bug 1695445] ssh-port config set is failing
-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Bugs mailing list