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 tests aren't very robust
(http://autopkgtest.ubuntu.com/packages/j/juju-core/yakkety/amd64/) and
apparently don't get automatically triggered with lxd updates.
Is there any collaboration/cross-CI between lxd and juju 2.0 to ensure
that juju keeps working? This is not only relevant for yakkety but also
for 16.04 LTS as you usually backport the new versions.
** Changed in: lxd (Ubuntu)
Status: New => Confirmed
--
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] Feature Exception for LXD in Ubuntu 16.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1618159/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
