I'd like to also confirm this bug, which we've been experiencing for the past few months since we first setup an 18.04 image for our deployment portal.
Initially I thought the cause MAY have been from us using ifupdown (we have to as our vCenter instance hasn't been upgraded to 6.5.x or 6.7 where Ubuntu 18.04 with NetPlan is officially supported). I've checked logs and it seems that *every time* apt upgrade is ran and one of the systemd components are upgraded, the network dies. You can do "ip addr" and see the interface has no addresses assigned. A simple restart of networking and the IPs come back. This literally just happened this morning to two of our 18.04 LTS systems and the systemd packages that were updated were: libsystemd0 systemd-sysv libpam-systemd systemd libnss-systemd The rest of the packages that were updated: grub-common grub2-common udev grub-pc apache2-data libudev1 grub-pc-bin apache2-bin libunistring2 apache2 apache2-utils I also had another report on Feb 20th, and it also involved the following updates: Start-Date: 2019-02-20 04:41:09 Commandline: /usr/bin/apt-get -o quiet=1 upgrade -y -o APT::Get::Show-Upgraded=true Upgrade: libsystemd0:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), udev:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), libudev1:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), systemd-sysv:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), libpam-systemd:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), systemd:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), libnss-systemd:amd64 (237-3ubuntu10.12, 237-3ubuntu10.13), pciutils:amd64 (1:3.5.2-1ubuntu1, 1:3.5.2-1ubuntu1.1), libpci3:amd64 (1:3.5.2-1ubuntu1, 1:3.5.2-1ubuntu1.1) End-Date: 2019-02-20 04:42:19 The interesting thing is, looking at my notes, in my case it MAY BE from the ifupdown which should "just work", as this 2nd VM also has that setup. I looked and it updated this morning the same as the first machine but I didn't have a report of it being offline. Now on this 2nd machine, I did also do an "apt remove netplan.io" as a "hope this solves the issue and it's some conflict or issue between netplan.io and ifupdown OR a conflict between systemd and netplan.io and since there's no report of it being down and I just verified networking is fine.... is it something between systemd and netplan? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782709 Title: Updating systemd kills network on bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
