It's kinda hard to tell what's going on because of all that systemd mess. It looks to me like there was somehow a leftover process from LXD 3.0.1 that'd keep the database open and prevent the 3.0.2 version from properly starting up and applying the update but without a system to poke at, it's hard to tell.
I also see a whole lot of reports of "kill -9" (SIGKILL) happening to the LXD process, it's not something that LXD itself or its packaging would do, so I'm wondering where that was coming from. Would you consider attempting the upgrade to 3.0.2 again? If it works, then I'm afraid there's not going to be enough information in here for us to track it down and fix it, so we'd likely close this issue and see if anyone else hits this on a system where we can grab some more information as it's happening. If it doesn't work and LXD gets stuck again, can you try: - sudo systemctl stop lxd.socket lxd.service - sudo pkill -9 lxd - sudo lxd --debug --group lxd That'd make sure there's no leftover LXD processes on the system then start LXD outside of the systemd unit and in debug mode. If something bad happens during the upgrade, that'd then make it pretty clear what's going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801957 Title: lxd upgrade hung during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1801957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
