=== sysop is now known as Guest27913 === Guest27913 is now known as Bashing-om [17:07] o/ [17:07] upgrading to systemd 246 breaks systemd-networkd until the service is restarted by hand [17:07] breaking DNS [17:07] Just upgraded to systemd 246-2ubuntu1. Getting a ton of errors like failed to start process error reports [17:07] reported to canonical IS eariler today as a possible bug in GCE but it turns out to be just systemd [17:08] there's also a bug in systemd-logind upgrade that is more fringe and sadly requires a reboot on most systems [17:08] tomreyn are you using lingering? [17:08] linger is affected by systemd-logind bug [17:08] (the bug is fixed in 246 but upgrade exposes you to it) [17:09] zyga-mbp: i don't use pre-release versions of ubuntu. [17:10] I use it on my thinkpad and we test snapd against it, in CI, since the day the archive opened [17:11] i suggest looking for existing bug reports and subscribing to them, or filing nerw ones if there are none, yet [17:11] *new (not nerw) [17:13] I found a bug in debian about it [17:13] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966612 [17:13] Debian bug 966612 in systemd "systemd-networkd failed to restart on upgrade to 246-1" [Minor,Fixed] [17:29] tomreyn: I ended up downgrading systemd to 245.7-1ubuntu1 [17:31] i see [21:27] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891716 [21:27] Launchpad bug 1891716 in systemd (Ubuntu) "Networking broken after systemd update" [Undecided,New] === sysop is now known as Guest23943 === Guest23943 is now known as Bashing-om