bullseye CI jobs fail on systemd

bullseye CI jobs fail on systemd

[Henning Schild]

Hi,

on several CI runs i saw bullseye failing on systemd postinst. There is
a new systemd version since 03/18 and i guess it might just be a
temporary upstream issue. I did not look further, instead removed
bullseye from CI for my builds.

Setting up systemd (244.3-1) ...
Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service -> /lib/systemd/system/getty@.service.
Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target -> /lib/systemd/system/remote-fs.target.
Created symlink /etc/systemd/system/dbus-org.freedesktop.timesync1.service -> /lib/systemd/system/systemd-timesyncd.service.
Created symlink /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service.
Initializing machine ID from random generator.
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error exit status 73

Henning

Re: bullseye CI jobs fail on systemd

[Jan Kiszka]

On 21.03.20 09:30, [ext] Henning Schild wrote:
> Hi,
> 
> on several CI runs i saw bullseye failing on systemd postinst. There is
> a new systemd version since 03/18 and i guess it might just be a
> temporary upstream issue. I did not look further, instead removed
> bullseye from CI for my builds.
> 
> Setting up systemd (244.3-1) ...
> Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service -> /lib/systemd/system/getty@.service.
> Created symlink /etc/systemd/system/multi-user.target.wants/remote-fs.target -> /lib/systemd/system/remote-fs.target.
> Created symlink /etc/systemd/system/dbus-org.freedesktop.timesync1.service -> /lib/systemd/system/systemd-timesyncd.service.
> Created symlink /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service.
> Initializing machine ID from random generator.
> dpkg: error processing package systemd (--configure):
>   installed systemd package post-installation script subprocess returned error exit status 73
> 

I'm seeing this now as well - but only with your series applied (you can 
see that in our internal CI, nightly runs). Given this, we should look 
more closely to avoid overseeing some regression. Or we managed to 
trigger an upstream issues that no many see and, thus, should be reported.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

Re: bullseye CI jobs fail on systemd

[Henning Schild]

Am Sun, 22 Mar 2020 18:09:49 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:

> On 21.03.20 09:30, [ext] Henning Schild wrote:
> > Hi,
> > 
> > on several CI runs i saw bullseye failing on systemd postinst.
> > There is a new systemd version since 03/18 and i guess it might
> > just be a temporary upstream issue. I did not look further, instead
> > removed bullseye from CI for my builds.
> > 
> > Setting up systemd (244.3-1) ...
> > Created symlink
> > /etc/systemd/system/getty.target.wants/getty@tty1.service ->
> > /lib/systemd/system/getty@.service. Created symlink
> > /etc/systemd/system/multi-user.target.wants/remote-fs.target ->
> > /lib/systemd/system/remote-fs.target. Created symlink
> > /etc/systemd/system/dbus-org.freedesktop.timesync1.service ->
> > /lib/systemd/system/systemd-timesyncd.service. Created symlink
> > /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
> > -> /lib/systemd/system/systemd-timesyncd.service. Initializing
> > machine ID from random generator. dpkg: error processing package
> > systemd (--configure): installed systemd package post-installation
> > script subprocess returned error exit status 73 
> 
> I'm seeing this now as well - but only with your series applied (you
> can see that in our internal CI, nightly runs). Given this, we should
> look more closely to avoid overseeing some regression. Or we managed
> to trigger an upstream issues that no many see and, thus, should be
> reported.

Thanks! Got to love caches and multiconfig ;). At least this one seems
reproducible.

Henning

> Jan
>