after a successful bootstrap, juju ssh 0 reports "machine not found" when -m controller not present
Bug #1815848 reported by
Tim McNamara
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
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?
Revision history for this message
| John A Meinel (jameinel) wrote Re: [Bug 1815848] [NEW] after a successful bootstrap, juju ssh 0 reports "machine not found" when -m controller not present | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → 2.6-beta1 |
| Changed in juju: | |
| milestone: | 2.6-beta1 → 2.6-beta2 |
| Changed in juju: | |
| milestone: | 2.6-beta2 → 2.6-rc1 |
| Changed in juju: | |
| milestone: | 2.6-rc1 → 2.6-rc2 |
| tags: | added: bitesize papercut ui |
| Changed in juju: | |
| milestone: | 2.6-rc2 → 2.6.1 |
| Changed in juju: | |
| milestone: | 2.6.1 → 2.6.2 |
| Changed in juju: | |
| milestone: | 2.6.2 → 2.6.3 |
| Changed in juju: | |
| milestone: | 2.6.3 → 2.6.4 |
| Changed in juju: | |
| milestone: | 2.6.4 → 2.6.5 |
| Changed in juju: | |
| milestone: | 2.6.5 → 2.6.6 |
| Changed in juju: | |
| milestone: | 2.6.6 → 2.6.7 |
| Changed in juju: | |
| milestone: | 2.6.7 → none |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
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:/
>
> 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:/
>