Hello Brad, or anyone else affected, Accepted lxc into wily-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.10.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments Status in lxc package in Ubuntu: Fix Committed Status in lxc source package in Trusty: In Progress Status in lxc source package in Vivid: Fix Committed Status in lxc source package in Wily: Fix Committed Status in lxc source package in Xenial: Fix Committed Bug description: I've just tried using juju to deploy to a container with trusty- proposed repo enabled, and I get an error message about 'failed to retrieve the template to clone'. The underlying error appears to be: tar --numeric-owner -xpJf /var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz; xz: (stdin): File format not recognized; tar: Child returned status 1; tar: Error is not recoverable: exiting now; This seems to be fairly obvious, trying to use xz on a tar.gz file is never going to work. The change appears to be from https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf, it assumes everything passed into it will be a .tar.xz file. This appears to be a conflict between the template expecting a .tar.xz file, and juju providing it a .tar.gz file. You can see what juju is providing from: $ ubuntu-cloudimg-query trusty released amd64 --format %{url} https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz From the juju deployed host: $ apt-cache policy lxc-templates lxc-templates: Installed: 1.0.8-0ubuntu0.1 Candidate: 1.0.8-0ubuntu0.1 Version table: *** 1.0.8-0ubuntu0.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status From the host running juju: $ apt-cache policy juju-core juju-core: Installed: 1.22.8-0ubuntu1~14.04.1 Candidate: 1.25.0-0ubuntu1~14.04.1~juju1 Version table: 1.25.0-0ubuntu1~14.04.1~juju1 0 500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 Packages *** 1.22.8-0ubuntu1~14.04.1 0 400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 Packages 100 /var/lib/dpkg/status All machine involved are running trusty: $ lsb_release -rd Description: Ubuntu 14.04.3 LTS Release: 14.04 Please let me know if you need any more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp