All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.9) for jammy have finished running. The following regressions have been reported in tests triggered by the package:
casync/2+20201210-1build1 (ppc64el) dpdk/21.11.3-0ubuntu0.22.04.1 (arm64) fwupd/1.7.9-1~22.04.1 (armhf) init-system-helpers/unknown (s390x) initramfs-tools/0.140ubuntu13.1 (amd64) libsdl2/2.0.20+dfsg-2ubuntu1.22.04.1 (s390x) libsoup3/3.0.7-0ubuntu1 (s390x) libvirt/8.0.0-1ubuntu7.4 (s390x) linux-lowlatency-hwe-5.19/5.19.0-1021.22~22.04.1 (amd64, arm64) linux-nvidia/5.15.0-1018.18 (amd64) mutter/42.5-0ubuntu1 (amd64) netplan.io/0.105-0ubuntu2~22.04.3 (arm64, s390x) network-manager/1.36.6-0ubuntu2 (s390x) nextepc/unknown (s390x) open-iscsi/2.1.5-1ubuntu1 (s390x) openrazer/3.2.0+dfsg-3 (i386) pdns-recursor/unknown (s390x) postgresql-14/unknown (s390x) pystemd/0.7.0-5build1 (s390x) samba/unknown (s390x) strongswan/unknown (s390x) systemd/249.11-0ubuntu3.9 (s390x) umockdev/0.17.7-1 (s390x) zfs-linux/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2000880 Title: systemd-networkd: ActivationPolicy ignored in VLANs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] The ActivationPolicy property in .network files is ignored for VLANs. [Test Plan] * On a Jammy machine with an interface named ens3, create the following configs: $ cat > /etc/systemd/network/10-vlan18.netdev << EOF [NetDev] Name=vlan18 Kind=vlan [VLAN] Id=18 EOF $ cat > /etc/systemd/network/20-vlan18.network << EOF [Match] Name=vlan18 [Network] Address=10.10.1.1/24 [Link] ActivationPolicy=manual EOF $ cat > /etc/systemd/network/30-ens3.network << EOF [Match] Name=ens3 [Network] DHCP=ipv4 VLAN=vlan18 EOF * Reboot the machine * On an affected machine, the vlan18@ens3 interface will have a configured IP at boot, despite the ActivationPolicy=manual setting in /etc/systemd/network/20-vlan18.network. On a patched machine, the interface should not have a configured IP. [Where problems could occur] The patch adds a condition where a netdev is not yet ready to be created. Specifically, it makes sure stacked netdevs are not created before their underlying link is activated. If we saw any problems, it would be related to netdev creation. [Original Description] This has been fixed upstream, see Upstream bug: https://github.com/systemd/systemd/issues/22593 Any chance of a backport of the fix to 22.04? Fix: https://github.com/systemd/systemd-stable/pull/211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
