All autopkgtests for the newly accepted systemd (237-3ubuntu10.34) for bionic have finished running. The following regressions have been reported in tests triggered by the package:
php7.2/7.2.24-0ubuntu0.18.04.2 (armhf) openssh/1:7.6p1-4ubuntu0.3 (arm64, armhf, ppc64el, amd64, s390x, i386) dovecot/1:2.2.33.2-1ubuntu4.5 (armhf) gvfs/1.36.1-0ubuntu1.3.3 (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/bionic/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/1845909 Title: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4 Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] in some situations when a networkd interface is configured with LinkLocalAddressing=no, networkd still assigns a link-local address to it [test case] see comment 3. note I was only able to reproduce this at boot time; if the vlan interface is removed (i.e. 'sudo ip l del pppoe') and then networkd restarted, the pppoe interface is created and does not have a link- local address. This is due to this bug being triggered by timing, as a vlan interface is raised by the kernel when its parent interface is raised, in this case by networkd itself. [regression potential] this changes how ipv6ll addresses are managed and dropped, as well as changing when foreign addresses are dropped (later in config process). Any regressions would likely be around incorrectly setting ipv6ll addresses, or complete failure to complete interface configuration. [scope] this is fixed upstream by: https://github.com/systemd/systemd/pull/13927 and also requires the upstream PR referenced in the original description: upstream patch: https://github.com/systemd/systemd/pull/13565 this is required for focal (uploaded already), eoan, and bionic. It may be required for xenial. [other info] Note, the original description below is incorrect, the issue/patch it references is not enough to fix this issue. original description: -- upstream issue: https://github.com/systemd/systemd/issues/12886 upstream patch: https://github.com/systemd/systemd/pull/13565 The upstream fix will be available in systemd 244. Backport please. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1845909/+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
