All autopkgtests for the newly accepted systemd (237-3ubuntu10.47) for bionic have finished running. The following regressions have been reported in tests triggered by the package:
openssh/1:7.6p1-4ubuntu0.3 (arm64, ppc64el, s390x, i386, armhf, amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) snapd/2.48.3+18.04 (s390x) systemd/237-3ubuntu10.47 (i386) polkit-qt-1/0.112.0-5 (ppc64el) network-manager/1.10.6-2ubuntu1.4 (amd64) linux-hwe-5.4/5.4.0-72.80~18.04.1 (i386) linux-gke-5.4/5.4.0-1040.42~18.04.1 (amd64) casync/2+61.20180112-1 (s390x) linux-hwe-5.0/5.0.0-65.71 (i386) ubuntu-drivers-common/1:0.8.6.3~0.18.04.1 (ppc64el) netplan.io/0.99-0ubuntu3~18.04.4 (i386) 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/1923115 Title: Networkd vs udev nic renaming race condition Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] systemd-networkd renames nic just after udev renamed it e.g kernel: [ 2.827368] vmxnet3 0000:0b:00.0 ens192: renamed from eth0 kernel: [ 7.562729] vmxnet3 0000:0b:00.0 eth0: renamed from ens192 systemd-networkd[511]: ens192: Interface name change detected, ens192 has been renamed to eth0. This cause netplan or the other network management pkg can't find proper nic sometimes. This happens on Bionic Below commit seems to solve this issue. https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b There are bunch of related commits but above one the customer tested it worked. [Test Plan] The customer has issue and they could help us to test this. Internally they already test this and it worked. Please refer to github issue's reproduction step as well. https://github.com/systemd/systemd/issues/7293#issue-272917058 where the test plan is described as: "Reboot a couple of times. Sometimes the interface is renamed correctly. Sometimes it is not." [Where problems could occur] systemd-networkd should be restarted for this patch. systemd-networkd nic renaming could have issue. renaming may not be happening unexpectedly. e.g doesn't rename it properly or rename it when it should do. [Others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+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
