Add MAAS 2.0 support in Juju 2.0
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Tim Penhey | ||
| juju-core |
Invalid
|
Undecided
|
Unassigned | ||
| 1.25 |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I am using fully updated/upraded Xenial Xersus with MAAS deployed successfully but when I try bootstrapping juju with "juju bootstrap" or juju-quickstart I always end with the same error.
ERROR cannot determine if environment is already bootstrapped.: could not access file '2a01aad3-
Regiond.log
2016-03-31 19:05:03 [-] /usr/lib/
2016-03-31 19:05:03 [-] 127.0.0.1 - - [31/Mar/
MAAS Version: 2.0.0~alpha4+
juju Version: 1.25.0-0ubuntu3
This happened as well with Alpha 3 of MAAS andd this is a completely fresh install
| Cheryl Jennings (cherylj) wrote | #1 |
| Changed in juju-core: | |
| status: | New → Invalid |
| status: | Invalid → In Progress |
| summary: |
- Cannot Bootrap MAAS 2.0 alpha 4. Could not access file ***-provider- - state requested map, got <nil> + Add MAAS 2.0 support for Juju 2.0 |
| summary: |
- Add MAAS 2.0 support for Juju 2.0 + Add MAAS 2.0 support in Juju 2.0 |
| Changed in juju-core: | |
| importance: | Undecided → High |
| garyx (garyx) wrote | #2 |
| Changed in juju-core: | |
| assignee: | nobody → Tim Penhey (thumper) |
| milestone: | none → 2.0.0 |
| Jonathan Tyler (ashcore) wrote | #3 |
| Changed in juju-core: | |
| status: | In Progress → Fix Released |
| Tim Penhey (thumper) wrote | #4 |
| Changed in juju-core: | |
| status: | Fix Released → Fix Committed |
| milestone: | 2.0.0 → 2.0-beta7 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta7 → none |
| milestone: | none → 2.0-beta7 |
| Changed in juju-core: | |
| status: | New → Invalid |
Juju is still working to support MAAS 2.0. The support for MAAS 2.0 will only be in Juju 2.