Control: severity -1 serious On Tue, May 26, 2020 at 06:35:50PM -0300, Antonio Terceiro wrote: > On Tue, May 26, 2020 at 12:55:10PM +0200, Inaki Malerba wrote: > > Source: lxc > > Version: 1:4.0.2-1 > > Severity: important > > > > Dear Maintainer, > > > > Since version 1:4.0.2-1, we've found a change on the behavior of > > lxc-stop when running on the Salsa-CI pipeline. > > > > debci calls `lxc-stop --quiet --kill --name $NAME` and it's returning > > exit code 1. > > > > This can be reproduced on salsa-ci pipeline, which calls `debci localtest`. > > > > https://salsa.debian.org/salsa-ci-team/pipeline/-/jobs/765946 > > > > <VirtSubproc>: failure: ['sudo', 'timeout', '600', 'lxc-stop', > > '--quiet', '--kill', '--name', 'ci-147-3f089355'] failed (exit status 1, > > stderr '') > > I have been using this version of lxc locally for autopkgtest for a > while without any issues, so this issue is probably specific to running > lxc under docker. > > is there an easy/documented way of reproducing the salsa ci environment > (i.e. lxc working under docker) locally? I downloaded > registry.salsa.debian.org/salsa-ci-team/pipeline/autopkgtest, started a > container with --privileged, and tried following the steps in the > salsa-ci-yml, but I am probably missing something because the containers > won't start apparently due to apparmor.
I'm upgrading this bug to serious to prevent this version from reaching testing since this breaks Debian infrastructure. :-)
signature.asc
Description: PGP signature