juju ssh MACHINE hangs for 5s when the machine doesn't exist

[John A Meinel]

If I do 'juju ssh 5' and that machine exists, it takes it about 2s to connect. However if I do "juju ssh 10" and that machine doesn't exist it hangs for about 5s before stating:
ERROR machine 10 not found

It doesn't make sense that a successful lookup can happen much faster than a failed lookup. (Certainly it doesn't have to do any SSH, etc).

Do we have something where we are "maybe the machine will show up withing 5s"? It feels like if we want to do something like that, we should be giving some sort of feedback to the user.

[John A Meinel (jameinel)]

Note that --debug doesn't give anything useful
$ juju ssh --debug 0
10:37:50 INFO juju.cmd supercommand.go:56 running juju [2.9.33 35a17f49f0fd6225211eaa9c70bb2223832c1db5 gc go1.18.3]
10:37:50 DEBUG juju.cmd supercommand.go:57 args: []string{"juju", "ssh", "--debug", "0"}
10:37:50 INFO juju.juju api.go:78 connecting to API addresses: [10.5.24.123:17070]
10:37:50 DEBUG juju.api apiclient.go:1153 successfully dialed "wss://10.5.24.123:17070/model/eb001ecd-2ba8-4681-8a58-b0776403b12f/api"
10:37:50 INFO juju.api apiclient.go:688 connection established to "wss://10.5.24.123:17070/model/eb001ecd-2ba8-4681-8a58-b0776403b12f/api"
10:37:50 DEBUG juju.cmd.juju.commands ssh_machine.go:338 proxy-ssh is false
10:37:55 DEBUG juju.api monitor.go:35 RPC connection died
ERROR machine 0 not found

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.