I've done some more digging into the systemd package update issue. We have a number of Ubuntu 18.04 hosts, most of them are virtual machines running simple eth0 configurations under Hyper-V. All of those VMs updated the systemd package without issue. The only hosts which had issues after the systemd package upgrade were the two SuperMicros running bonded 10G interfaces. On both of those hosts, the bond defined in netplan seems to have lost its configuration during the systemd upgrade. There were multiple kern.log messages regarding the bond leaving one of its ports in a disabled state after the update. Both hosts logged this on the same second that dpkg.log shows the systemd package itself entering 'status installed', so I'm confident it was that systemd package rather than pam-systemd that followed several seconds later.
I am still willing to provides logs and configurations if you tell me what you need to see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
