Le mardi 26 mai 2020 à 12:55:10+0200, Inaki Malerba a écrit :
> 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 '')

Could you remove the --quiet bit to see if lxc-stop gives us a bit more
intel?

If possible, have your testbed call lxc-stop --kill --logpriority trace
--logfile /dev/stdout --name ${NAME}, so we can have the most expressive
output. But if it's an error, removing the quiet bit could be enough.

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.

Attachment: signature.asc
Description: PGP signature

Reply via email to