Juju seems confused about a newly defined MAAS cloud
Bug #1582065 reported by
Mark Shuttleworth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned |
Bug Description
Just saw this:
mark@maas:~$ juju bootstrap gmaas local:gmaas
ERROR unknown cloud "local:gmaas", please try "juju update-clouds"
Which is unexpected because:
mark@maas:~$ juju list-clouds
CLOUD TYPE REGIONS
...
localhost lxd localhost
local:gmaas maas
So local:gmaas is there but it cannot be used to bootstrap!
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.0-beta8 |
tags: | added: juju-release-support maas-provider usability |
Changed in juju-core: | |
milestone: | 2.0-beta8 → 2.0-beta9 |
Changed in juju-core: | |
milestone: | 2.0-beta9 → 2.0-beta10 |
Changed in juju-core: | |
milestone: | 2.0-beta10 → 2.0-beta11 |
Changed in juju-core: | |
milestone: | 2.0-beta11 → 2.0-beta12 |
Changed in juju-core: | |
milestone: | 2.0-beta12 → 2.0-beta13 |
Changed in juju-core: | |
milestone: | 2.0-beta13 → 2.0-beta14 |
Changed in juju-core: | |
milestone: | 2.0-beta14 → 2.0-beta15 |
Changed in juju-core: | |
milestone: | 2.0-beta15 → 2.0-beta16 |
Changed in juju-core: | |
milestone: | 2.0-beta16 → 2.0-beta17 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta17 → none |
milestone: | none → 2.0-beta17 |
Changed in juju: | |
milestone: | 2.0-beta17 → 2.0-beta18 |
Changed in juju: | |
milestone: | 2.0-beta18 → 2.0-beta19 |
Changed in juju: | |
milestone: | 2.0-beta19 → 2.0-rc1 |
To post a comment you must log in.
This may be caused by explicitly specifying "local:" prefix.
I *think* it works without specifying the prefix but needs to be addressed to work for both case - with and without prefix.