All autopkgtests for the newly accepted systemd (242-7ubuntu3.9) for eoan have finished running. The following regressions have been reported in tests triggered by the package:
nghttp2/unknown (armhf) pulseaudio/unknown (armhf) docker.io/unknown (armhf) csync2/unknown (armhf) network-manager/unknown (armhf) dovecot/unknown (armhf) open-iscsi/unknown (armhf) netplan.io/unknown (armhf) asterisk/1:16.2.1~dfsg-2build2 (arm64) tinyssh/unknown (armhf) puppet/unknown (armhf) corosync/unknown (armhf) python-uinput/unknown (armhf) nextepc/unknown (armhf) debci/unknown (armhf) pyudev/unknown (armhf) cups/unknown (armhf) umockdev/0.13.2-1 (armhf) cockpit/unknown (ppc64el) network-manager/1.20.4-2ubuntu2.2 (arm64) nftables/unknown (armhf) prometheus/unknown (armhf) corosync-qdevice/unknown (armhf) prometheus-bind-exporter/unknown (armhf) python-systemd/unknown (armhf) prometheus-alertmanager/unknown (armhf) ndctl/unknown (armhf) prometheus-apache-exporter/unknown (armhf) dpdk/unknown (armhf) nextepc/0.3.10+nods-3ubuntu1 (ppc64el) dbus/unknown (armhf) openssh/1:8.0p1-6build1 (armhf, amd64, i386, ppc64el, arm64, s390x) openrazer/unknown (armhf) gvfs/1.42.1-1ubuntu1 (arm64) snapd/2.42.1+19.10 (i386) prometheus-node-exporter/unknown (armhf) prometheus-postgres-exporter/unknown (armhf) python-dbusmock/unknown (armhf) systemd/242-7ubuntu3.9 (ppc64el) 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/eoan/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/1877271 Title: networkd does not enable ipv6 when requested Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Eoan: Fix Committed Bug description: [impact] if networkd is configured with ipv6 address but the 'disable_ipv6' sysctl is enabled, networkd does not enable it and set the ipv6 configuration. [test case] [Match] Name=ens3 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=2001:db8::100/64 manually disable ipv6 for the interface: ubuntu@lp1859862-b:~$ echo 1 | sudo tee /proc/sys/net/ipv6/conf/ens3/disable_ipv6 1 the interface should not contain any ipv6 addresses: ubuntu@lp1859862-b:~$ ip -6 a show ens3 ubuntu@lp1859862-b:~$ restart networkd; it should enable ipv6 as ipv6 addresses are configured, but it does not: ubuntu@lp1859862-b:~$ sudo systemctl restart systemd-networkd ubuntu@lp1859862-b:~$ ip -6 a show ens3 ubuntu@lp1859862-b:~$ [regression potential] any regression would likely result in failure to configure ipv6 addresses/routes. [scope] this is needed only for Eoan. this is fixed by commit 57ad76074670d4859e808a6aabd69fd6e58514c5, which is included starting in v243, so this is fixed in Focal and later. this bug was introduced by a series of patches starting at 54a1a535bd60f13964bbddd8f381601e33e8e56f, which is included starting in v243, but was also pulled into Debian v242-4, and so included in Eoan. This bug is not present in earlier versions so is not needed in Xenial or Bionic. [other info] this is a follow on for the fix in bug 1859862. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877271/+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
