Bug#997006: closed by Debian FTP Masters <ftpmaster at ftp-master.debian.org> (reply to Michael Biebl <biebl at debian.org>) (Bug#997006: fixed in systemd 247.3-7)

Linus Lüssing linus.luessing at c0d3.blue
Wed Mar 23 23:45:21 GMT 2022


Just tried 247.3-7 and it fixes the LXD systemd-networkd issue for
me. Thanks a lot for your great maintenance work, will forward the
good news to the LXD forum once it propagates from
stable-proposed-updates to stable. I'm sure a lot of people there
will be happy about this, too.

Regards, Linus


On Mon, Mar 21, 2022 at 12:48:19PM +0000, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the systemd package:
> 
> #997006: systemd-networkd: broken/regression in unprivileged LXD container in v247
> 
> It has been closed by Debian FTP Masters <ftpmaster at ftp-master.debian.org> (reply to Michael Biebl <biebl at debian.org>).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters <ftpmaster at ftp-master.debian.org> (reply to Michael Biebl <biebl at debian.org>) by
> replying to this email.
> 
> 
> -- 
> 997006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997006
> Debian Bug Tracking System
> Contact owner at bugs.debian.org with problems

> Date: Mon, 21 Mar 2022 12:47:07 +0000
> From: Debian FTP Masters <ftpmaster at ftp-master.debian.org>
> To: 997006-close at bugs.debian.org
> Subject: Bug#997006: fixed in systemd 247.3-7
> 

> Date: Fri, 22 Oct 2021 11:43:47 +0200
> From: Linus Lüssing <linus.luessing at c0d3.blue>
> To: Debian Bug Tracking System <submit at bugs.debian.org>
> Subject: systemd-networkd: broken/regression in unprivileged LXD container
>  in v247
> 
> Package: systemd
> Version: 247.3-6
> Severity: normal
> Tags: upstream
> X-Debbugs-Cc: linus.luessing at c0d3.blue
> 
> Hi,
> 
> We found that using systemd-networkd in an unprivileged LXD container is
> broken in systemd v247. A network or link file is not attached to an
> interface and instead "networkctl -l status eth0" shows "n/a" for the
> "Link File" and "Network File". Leading to the network interface not being
> configured at all. systemd v246 and v248/v249 work fine, so it is a
> regression specific to v247.
> 
> Bisect'ing shows that this commit introduced the bug for v247:
> 
> https://github.com/systemd/systemd/commit/88da55e28b467999da005591d3252a98f4436522
> 
> And the following commit fixed it again for v248:
> 
> https://github.com/systemd/systemd/commit/0e789e6d48046d43c50dd949a71ac56f1127bb96
> 
> Git cherry-picking 0e789e6d4 onto v247 fixes the issue (cherry-picking does
> not apply cleanly but resolving this is straight forward).
> 
> Furthermore systemd-networkd does not work if the udev package is
> missing (same symptoms, no link or network file gets attached to the
> interface).
> 
> 
> Suggestions to fix:
> 
> * Add a dependency to the systemd package for the udev package.
> * Backport 0e789e6d4 to the systemd v247 package.
> 
> Alternatively (or additionally) systemd v249 could be added to
> bullseye-backports, so people using Debian Bullseye could work around
> the issue by installing systemd v249.
> 
> For more details see the following links:
> 
> https://discuss.linuxcontainers.org/t/systemd-networkd-not-working-in-debian-sid-or-bullseye-images/11503/17
> https://github.com/systemd/systemd/pull/18559
> 
> Regards, Linus
> 
> 
> 
> -- Package-specific info:
> 
> -- System Information:
> Debian Release: 11.1
>   APT prefers stable-security
>   APT policy: (500, 'stable-security'), (500, 'stable')
> Architecture: arm64 (aarch64)
> 
> Kernel: Linux 5.9.2-v8+ (SMP w/4 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_CRAP
> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages systemd depends on:
> ii  adduser                          3.118
> ii  libacl1                          2.2.53-10
> ii  libapparmor1                     2.13.6-10
> ii  libaudit1                        1:3.0-2
> ii  libblkid1                        2.36.1-8
> ii  libc6                            2.31-13+deb11u2
> ii  libcap2                          1:2.44-1
> ii  libcrypt1                        1:4.4.18-4
> ii  libcryptsetup12                  2:2.3.5-1
> ii  libgcrypt20                      1.8.7-6
> ii  libgnutls30                      3.7.1-5
> ii  libgpg-error0                    1.38-2
> ii  libip4tc2                        1.8.7-1
> ii  libkmod2                         28-1
> ii  liblz4-1                         1.9.3-2
> ii  liblzma5                         5.2.5-2
> ii  libmount1                        2.36.1-8
> ii  libpam0g                         1.4.0-9+deb11u1
> ii  libseccomp2                      2.5.1-1
> ii  libselinux1                      3.1-3
> ii  libsystemd0                      247.3-6
> ii  libzstd1                         1.4.8+dfsg-2.1
> ii  mount                            2.36.1-8
> ii  systemd-timesyncd [time-daemon]  247.3-6
> ii  util-linux                       2.36.1-8
> 
> Versions of packages systemd recommends:
> ii  dbus  1.12.20-2
> 
> Versions of packages systemd suggests:
> pn  policykit-1        <none>
> pn  systemd-container  <none>
> 
> Versions of packages systemd is related to:
> pn  dracut           <none>
> pn  initramfs-tools  <none>
> ii  libnss-systemd   247.3-6
> ii  libpam-systemd   247.3-6
> pn  udev             <none>
> 
> -- Configuration Files:
> /etc/systemd/journald.conf changed:
> [Journal]
> 
> /etc/systemd/logind.conf changed:
> [Login]
> 
> /etc/systemd/resolved.conf changed:
> [Resolve]
> 
> 
> -- no debconf information



More information about the Pkg-systemd-maintainers mailing list