Broken juju LXC deployments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
High
|
Stéphane Graber | ||
Trusty |
Fix Released
|
High
|
Stéphane Graber | ||
Vivid |
Fix Released
|
High
|
Stéphane Graber | ||
Wily |
Fix Released
|
High
|
Stéphane Graber | ||
Xenial |
Fix Released
|
High
|
Stéphane Graber |
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/
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:/
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-
https:/
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://
100 /var/lib/
From the host running juju:
$ apt-cache policy juju-core
juju-core:
Installed: 1.22.8-
Candidate: 1.25.0-
Version table:
1.
500 http://
*** 1.22.8-
400 http://
100 /var/lib/
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.
CVE References
tags: | added: regression-proposed trusty |
Changed in lxc (Ubuntu): | |
importance: | Undecided → Medium |
tags: |
added: verification-done removed: verification-needed |
Oh yeah, I can see how this is going to be a problem.
I'll look at changing the code path to use auto-detected compression rather than specific one.
The reason for this change in the first place is that the .tar.gz images will be deprecated in favor for .tar.xz, so I'd recommend JuJu also switch to .tar.xz at some point soon (I don't believe the cloud team has set a timeframe for phasing out tar.gz yet, but it's planned).