[Bug 1519677] Re: add lxd backend
Launchpad Bug Tracker
1519677 at bugs.launchpad.net
Fri Dec 18 07:11:42 UTC 2015
This bug was fixed in the package autopkgtest - 3.19
---------------
autopkgtest (3.19) unstable; urgency=medium
New features/behaviour changes:
* Add adt-virt-lxd runner for LXD. (LP: #1519677)
* Add adt-build-lxd tool for building or updating an LXD image with
standard autopkgtest customizations applied. This is similar to
adt-build-lxc.
* Unify test bed setup scripts for VMs (adt-setup-vm), containers (in
adt-build-lxc) and cloud (setup-commands/cloud-vm-setup) into a common
script setup-commands/setup-testbed. This will work both for image
building (VM, cloud, LXC, LXD) and as --setup-commands (in which case some
actions are skipped).
* setup-commands/setup-testbed: Clean up many more packages. Only do this
when building an image, to avoid accidentally destroying testbeds which
are not minimal autopkgtest ones.
* Make --env apply to package builds too. With that you can e. g. set
DEB_BUILD_OPTIONS.
* Add new action type --git-source which installs git (unless already
present), checks out a remote branch, and then behaves like
--unbuilt-tree.
* adt-virt-lxc.1: Mention adt-build-lxc in "Requirements".
Bug fixes:
* If apt-get fails when installing test dependencies and apt
pinning is in use, also retry without pinning. This was already done in
the case of apt-get succeeding but removing our "satdep" dummy package
(the common case), but this does not cover upgrades of Priority: >=
important packages which make apt-get exit with non-zero.
* Set $TERM in testbed to the host's value when starting an interactive
shell in the testbed. This fixes broken shells with the LXC/LXD runners.
-- Martin Pitt <mpitt at debian.org> Thu, 17 Dec 2015 16:45:54 +0100
** Changed in: autopkgtest (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autopkgtest in Ubuntu.
https://bugs.launchpad.net/bugs/1519677
Title:
add lxd backend
Status in autopkgtest package in Ubuntu:
Fix Released
Bug description:
LXD is the direction that the LXC project is moving towards, and it
has several nice features that are helpful for autopkgtest: fast
container creation with intelligent caching, support for local images
(with autopkgtest modifications), and seamless support for remote
containers.
We need the latter for moving armhf testing into Scalingstack, as we
don't have native armhf support there. We can create a big semi-
permanent arm64 instance and then create armhf lxd containers in
that, and talk to them from the autopkgtest controller node in
ProdStack using the arm64 instance as a remote. This cannot be done
with either the ssh runner (that would need some rather complicated
setup script) nor the lxc runner (I tried wrapping ssh around it, but
the extra level of shell processing/quoting breaks stuff).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1519677/+subscriptions
More information about the foundations-bugs
mailing list