touch-packages team mailing list archive

[Launchpad Bug Tracker <1515463@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lxc - 1.1.5-0ubuntu2

---------------
lxc (1.1.5-0ubuntu2) xenial; urgency=medium

  * Cherry-pick from upstream:
    - Fix ubuntu-cloud template to detect compression algorithm instead
      of hardcoding xz. Also update list of supported releases and use trusty
      as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
    meant to be used by developers and by automated testing.

 -- Stéphane Graber <stgraber@xxxxxxxxxx>  Fri, 13 Nov 2015 12:05:36
-0500

** Changed in: lxc (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
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 Released
Status in lxc source package in Trusty:
  Fix Committed
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 Released

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