ERROR retrieving SSH host keys for ...: keys not found

[Casey Marshall]

This is a UX problem, but it was noticeable enough that I feel like it could trip up new users.

Deployed a service and tried to SSH in to see what was going on. I got this error until the service is "up" enough to have registered its keys (as I imagine it):

$ juju ssh prometheus/2
ERROR retrieving SSH host keys for "prometheus/2": keys not found

After a while, `juju ssh` succeeds. I don't think that error message is very clear to most users though. If this was my first time with Juju, I might conclude there was a persistent issue with that workload and conclude that "juju is broken".

This is also seen in CI
    http://reports.vapour.ws/releases/issue/57961a62749a567e39534c3c

[Cheryl Jennings (cherylj)]

I also see this error before the error retrieving SSH host keys:

$ juju ssh ubuntu/0
ERROR no public address

It would be nice to state that the machine / unit isn't ready instead of these errors.

[Menno Finlay-Smits (menno.smits)]

Thanks for picking up on this. I agree that this should be better.

How about if it looked something like this?

$ juju ssh prometheus/2
ERROR no SSH host keys available yet (agent is being provisioned?)

The "no public address" issue is related. I agree that should be better too. At a minimum we could do something like this:

$ juju ssh ubuntu/0
ERROR no public address available yet

It would be even better if the controller checked the provisioning status of the machine when there's no address or SSH keys available so that it could say something like:

$ juju ssh ubuntu/0
ERROR target machine is still being provisioned

Suggestions for improvement welcome.

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

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.