Add MAAS 2.0 support in Juju 2.0

Bug #1564577 reported by garyx
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
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-b42f-4d34-84ab-5d51d7b33d30-provider-state': Requested map, got <nil>.

Regiond.log

2016-03-31 19:05:03 [-] /usr/lib/python3/dist-packages/django/templatetags/future.py:25: django.utils.deprecation.RemovedInDjango19Warning: Loading the `url` tag from the `future` library is deprecated and will be removed in Django 1.9. Use the default `url` tag instead.
2016-03-31 19:05:03 [-] 127.0.0.1 - - [31/Mar/2016:19:05:02 +0000] "GET /MAAS/accounts/login/?next=%2FMAAS%2Fapi%2F1.0%2Ffiles%2F2a01aad3-b42f-4d34-84ab-5d51d7b33d30-provider-state%2F HTTP/1.1" 200 1657 "http://10.20.40.2/MAAS/api/1.0/files/2a01aad3-b42f-4d34-84ab-5d51d7b33d30-provider-state/" "Go-http-client/1.1"

MAAS Version: 2.0.0~alpha4+bzr4843-0ubuntu1
juju Version: 1.25.0-0ubuntu3

This happened as well with Alpha 3 of MAAS andd this is a completely fresh install

Revision history for this message
Cheryl Jennings (cherylj) wrote :

Juju is still working to support MAAS 2.0. The support for MAAS 2.0 will only be in Juju 2.

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
Revision history for this message
garyx (garyx) wrote :

Juju2 needs to be added into Ubuntu's 16.04 repositories as well in this case, they are not available there by default.

Tim Penhey (thumper)
Changed in juju-core:
assignee: nobody → Tim Penhey (thumper)
milestone: none → 2.0.0
Revision history for this message
Jonathan Tyler (ashcore) wrote :

Shit, did that by mistake, sorry.

Changed in juju-core:
status: In Progress → Fix Released
Revision history for this message
Tim Penhey (thumper) wrote :

Should be fully working with the next beta :-)

Changed in juju-core:
status: Fix Released → Fix Committed
milestone: 2.0.0 → 2.0-beta7
Curtis Hovey (sinzui)
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers