On Thu, Aug 18, 2016 at 04:52:48PM +0000, Rick Harding wrote: > It was caught today in Juju testing that we fail to build with the latest > lxd 2.1 [1]. This initially seems like it's an issue in that the team > checks for lxd versioning much too tightly. We're working to update this as > fast as possible and doing some testing to see what's new in 2.1 that might > cause any issues. > > In the mean time, please be aware when upgrading that if you upgrade lxd to > 2.1 you will not be able to use lxd with it until we get our updates in > place. > > Rick > > 1: https://bugs.launchpad.net/juju-core/+bug/1614559
Hi Rick, Hmm, so it looks like Juju itself is parsing the LXD version and failing? That's a bit weird as I'd have expected it to instead check for the API version (1.0) if even checking anything. I've been using the Juju betas with the git version of LXD on my machines without any problem, up until the time where I actually tagged LXD 2.1. So I don't think there is any actual problem with the new LXD and Juju, other than what looks like a buggy version check :) Oh, also, LXD only ever shows you the public part of the certificate, it doesn't expose the private key, so it's perfectly fine to include the log in bug reports. -- Stéphane Graber Ubuntu developer http://www.canonical.com
signature.asc
Description: PGP signature
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
