Bug#934992: network-manager breaks systemd autopkgtest

Michael Biebl biebl at debian.org
Sun Aug 18 18:26:59 BST 2019


Control: reassign -1 systemd 241-7

Am 18.08.19 um 18:39 schrieb Michael Biebl:
> Am 18.08.19 um 17:18 schrieb Michael Biebl:

>> I've created an LXC container via
>> autopkgtest-build-lxc debian bullseye
>> and got the same autopkgtest failure using this container.
>> So this looks like a regression that was introduced outside of
>> systemd/network-manager
>>
>> I've also tried a qemu backed autopkgtest run and there the tests
>> completed successfully.
>> Might this be a regression introduced by LXC itself (and or in
>> combination with a newer kernel?)
> 
> My test system is running unstable, i.e. I was using
> lxc_1:3.1.0+really3.0.4-1
> After downgrading lxc to 1:3.1.0+really3.0.3-8, boot-smoke did
> successfully pass again.
> 
> Paul, which lxc version was used to run the autopkgtest tests?
> 
> Is it possible to get access to a system with the exact same
> configuration as on ci.debian.net so one can interactively debug this issue?

Dear lxc maintainers, sorry for the noise.
Afaics this is actually a bug in the boot-smoke autopkgtest and not
related to lxc, so tentatively reassigning to systemd.

Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190818/95613d52/attachment-0001.sig>


More information about the Pkg-systemd-maintainers mailing list