Juju 2 is using a LXD API that is not in the released version of LXD 2.0

Bug #1597342 reported by Andrew McDermott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Andrew McDermott

Bug Description

Commit '4d46c861d6a672e1cdb021bff667ca52bed05255' has ended up using an API that did not make the LXD 2.0 API cut off. We should revert this change and the associated semantics of having a profile per container. This LXD API change will only be available in the next major release of LXD.

Revision history for this message
Andrew McDermott (frobware) wrote :
Changed in juju-core:
importance: Undecided → High
status: New → In Progress
description: updated
Revision history for this message
Andrew McDermott (frobware) wrote :

I reworked my branch and it now requires some additional testing, particularly on MAAS, but should be good to land tomorrow.

Changed in juju-core:
milestone: none → 2.0-beta13
Changed in juju-core:
milestone: 2.0-beta13 → 2.0-beta12
Revision history for this message
Andrew McDermott (frobware) wrote :
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta12 → none
milestone: none → 2.0-beta12
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.