Tobias, sorry for being so long in coming back around to this, but I followed a pointer to this bug from another one and am now trying to understand the regression that you're describing.
You described this as "bricking" your servers, but per the SRU regression analysis: Running [networkd] before dbus.service is running has two consequences: - It cannot immediately expose its D-Bus status interface. But it will retry every 5 s until that succeeds, so the D-Bus status interface will continue to work. (see test case) That seems to have some relation to your screenshot, which shows systemd-networkd failing and being retried. But I wouldn't have understood from the SRU description that the service would *fail* to start and be retried by systemd, and that doesn't explain it leading to a "brick" situation. The screenshot points to systemctl status systemd-networkd.service for details. Are you able to capture any of those details? Can you give us information on how to reproduce this hang so that we might debug it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
