I followed up with my coworker who originally built our two misbehaving boxes. He also ended up having to reboot the second box I left for him, to get the br01 bridge configuration back in working order. Simply running 'netplan apply' and restarting the systemd network service did not resolve it, but a full reboot did. We are using the default 18.04 netplan setup, we haven't reversed back to ifupdown like the other reporter.
Both hosts lost their networking immediately after the systemd update was applied this morning, which installed version 237-3ubuntu10.19. I can delve through them to find any logs or config files you want. These are Supermicro rack mounts with dual 10G interfaces, built as headless servers, so no ubuntu-desktop or X11 is installed on them. We have sssd installed on these with the required pam customizations to configure sssd to live in our Active Directory environment. pam-auth- updated printed about local mods to common-* so it wasn't updating. Those are the only unusual outputs from this mornings unattended- upgrades-dpkg.log file. I can attach any logs or other files you care to view. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
