Units with multiple IPs and SSH on a non-standard port fails reachability check
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Jack Shaw |
Bug Description
I've come across an issue with the "Juju SSH" experience for units with multiple IP addresses, when SSH is run on a non-standard port.
I have a host who's unit name is ppa/1, and machine number is 17. It has sshd listening on its IPv4 address (10.131.66.124), port 922.
With the following example, this is the contents of ~/.ssh/config:
>Host 10.131.66.124
> User ubuntu
> Port 922
I can access the unit with "juju ssh <ipv4>":
>myuser@myhost:~$ juju ssh 10.131.66.124
>Welcome to Ubuntu 16.04.7 LTS (GNU/Linux 4.4.0-223-generic x86_64)
However, if I try to "juju ssh" to the unit name or machine number:
>myuser@myhost:~$ juju ssh ppa/1
>ERROR cannot connect to any address: [10.131.66.124:22 252.124.0.1:22 [2620:2d:
>myuser@myhost:~$ juju ssh 17
>ERROR cannot connect to any address: [10.131.66.124:22 252.124.0.1:22 [2620:2d:
>myuser@myhost:~$ juju ssh 17 -v
>ERROR cannot connect to any address: [10.131.66.124:22 252.124.0.1:22 [2620:2d:
When running with "juju --debug", this is what I get: https:/
This looks to originate from https:/
We have a workaround for this (juju ssh <ipv4 address>), but being able to "juju ssh <unit-name>" would make for a much better user experience. Is there any way we can customise hostPorts for ReachableChecker?
tags: | added: ssh |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Jack Shaw (jack-shaw) |
Would the --port argument enough in your case?