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

[Joi Owen]

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
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