Bug#821037: adt-virt-lxc: leaves used containers behind

2020-10-25 Thread Paul Gevers
Hi all, On Sun, 22 Mar 2020 12:17:08 +0100 Paul Gevers wrote: > We're seeing this quite a lot currently on our ci.d.n infrastructure, > and maybe also on Ubuntu's infra, as reported in bug #908193 (I'm not > sure if that is actually a duplicate or different.) Another example:

Bug#821037: adt-virt-lxc: leaves used containers behind

2020-03-22 Thread Paul Gevers
tag 821037 - moreinfo thanks Hi, On Tue, 26 Apr 2016 08:57:13 +0200 Martin Pitt wrote: > Antonio Terceiro [2016-04-14 18:06 -0300]: > > When using adt-virt-lxc, sometimes containers will not be properly shut > > down, > > or not properly destroyed. > > Do you have the corresponding adt-run

Bug#821037: adt-virt-lxc: leaves used containers behind

2016-04-26 Thread Martin Pitt
Control: tag -1 moreinfo Hello Antonio, Antonio Terceiro [2016-04-14 18:06 -0300]: > When using adt-virt-lxc, sometimes containers will not be properly shut down, > or not properly destroyed. Do you have the corresponding adt-run logs? I'd like to check what happened there, either the cleanup

Bug#821037: adt-virt-lxc: leaves used containers behind

2016-04-14 Thread Antonio Terceiro
Package: autopkgtest Version: 3.20.3 Severity: normal When using adt-virt-lxc, sometimes containers will not be properly shut down, or not properly destroyed. For example, on one of the Debian CI workers I have this: root@ci-arm64-01:~# lxc-ls --fancy NAME STATEIPV4