LXD itself doesn't interact with systemd, so I'm not sure how waitready would know that the main systemd unit failed.
What waitready does is attempt to talk to the LXD API (which will be blocking due to lxd's socket activation), calling an internal REST API endpoint to wait for LXD's early initialization to complete. As for your database being unhappy, when did that happen? Is that on initial upgrade to 3.0 from 2.21 or what exactly was the upgrade sequence involved here? It should be reasonably easy to have LXD re-convert the database, likely fixing the problem, but I'd like to figure out when it broke to see if it's one of the issues that we have since resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765699 Title: lxd fails to start main process, yet waitready doesn't bail out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1765699/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
