juju ssh gives i/o timeout if latency is more than 500ms
Bug #2009008 reported by
Vidar Tyldum
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
We have a remote site with an RTT of about 580ms, and "juju ssh" will fail with an i/o timeout during the host key checking phase.
50:09 DEBUG juju.network.ssh reachable.go:156 dialing 111.111.173.32:22 to check host keys
09:50:09 DEBUG juju.network.ssh reachable.go:156 dialing 111.111.171.186:22 to check host keys
09:50:10 DEBUG juju.network.ssh reachable.go:159 dial 111.111.173.32:22 failed with: dial tcp 10.104.173.32:22: i/o timeout
09:50:10 DEBUG juju.network.ssh reachable.go:159 dial 111.111.171.186:22 failed with: dial tcp 10.104.171.186:22: i/o timeout
I could reproduce this by simulating the latency with tc:
sudo tc qdisc add dev ens3 root netem delay 510ms
tags: | added: ssh timeout |
tags: | removed: timeout |
Changed in juju: | |
importance: | Undecided → Medium |
status: | New → Triaged |
To post a comment you must log in.
Just confirming that this patch works (up to 1 second RTT) for juju v2.9: /github. com/tyldum/ juju/commit/ df22134ddc360fd 95bffff5b9cb0fe 2c58a8caba
https:/