Two of our Ubuntu 18.04 hosts applied this update this morning and both
dropped offline.  They're both using netplan and have bonded interfaces.
The bond layer was offline.  I had to reboot to get the network stack
running again.  I left one host offline so the coworker who configured
them can look it over later this morning.  Two identical hosts did not
apply this systemd update this morning and they're both still online.

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

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

Reply via email to