after a successful bootstrap, juju ssh 0 reports "machine not found" when -m controller not present

[Tim McNamara]

After bootstrapping successfully, but when nothing has been deployed, `juju ssh 0` reports "machine not found". To me, this feels like the wrong message: the machine is present, but the wrong model has been selected.

Perhaps add a hint that "-m controller" might have been intended?

[John A Meinel (jameinel)]

you could say:
  no machine "0" in model "default"
which might give you the hint

On Thu, Feb 14, 2019 at 6:55 AM Tim McNamara <email address hidden>
wrote:

> Public bug reported:
>
> After bootstrapping successfully, but when nothing has been deployed,
> `juju ssh 0` reports "machine not found". To me, this feels like the
> wrong message: the machine is present, but the wrong model has been
> selected.
>
> Perhaps add a hint that "-m controller" might have been intended?
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1815848
>
> Title:
> after a successful bootstrap, juju ssh 0 reports "machine not found"
> when -m controller not present
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1815848/+subscriptions
>

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

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