This bug was fixed in the package lxd - 2.4-0ubuntu1
---
lxd (2.4-0ubuntu1) yakkety; urgency=medium
* New upstream release (2.4) (LP: #1618159):
- Add API support for push based migration (with a client acting as relay)
- Add a new used_by property to profiles (similar to ne
Hello Stéphane, or anyone else affected,
Accepted lxd into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxd/2.4-0ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
** Changed in: lxd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: lxd (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618159
Title:
[FFe] F
There is ongoing work on the Juju side to better test their LXD provider
by at the very least, properly triggering on new LXD uploads.
On my side, I do test Juju before new LXD releases. We missed that 2.1
issue because I ran my tests right before actually changing the version
string (which I do l
In particular, the tests currently fail with
2016-08-19 22:44:11 ERROR cmd supercommand.go:458 invalid config: lxd
version 2.1, juju needs at least 2.0.0
which is obviously a misparsing of the version number by juju, but this
might hide real problems.
--
You received this bug notification becau
LXD has a proven track record of upstream and downstream CI and API
stability, and as LTS+1 yakkety is more or less a playground to try new
things (and not a production platform), so I'm generally fine with this.
AFAICS the highest risk here is that this inadvertently breaks juju-2.0
-- juju's own
