[Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces

[Joi Owen]

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
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1823871

Title:
  After unattended-upgrade of systemd IP configuration removed from
  interfaces

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Info:
  Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018).
  HP DL380 server

  I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface.
  I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log:

  Start-Date: 2019-04-09  06:15:01
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:07

  Start-Date: 2019-04-09  06:15:12
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:56

  Start-Date: 2019-04-09  06:15:59
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:16:15

  
  After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions