I got the initial assessment wrong, thanks Heinrich for clearing up that confusion :)
Here is what happened here: On Jammy, lxd-agent-loader (0.5) is configured to start lxd-agent.service when the multi-user.target was reached coupled with a ConditionPathExists=/dev/virtio-ports/org.linuxcontainers.lxd This means it would do nothing if that virtio-ports device was missing. On Noble, lxd-agent-loader (0.6) was changed to have udev start lxd- agent.service only when it sees a virtio-ports LXD knows. Along with that change, the ConditionPathExists was removed as no longer relevant. Heinrich did a distro-upgrade moving lxd-agent-loader from 0.5 -> 0.6 but this left behind the following symlinks: ``` /etc/systemd/system/multi-user.target.wants/lxd-agent.service /etc/systemd/system/multi-user.target.wants/lxd-agent-9p.service ``` Causing lxd-agent.service to always want to start, even if the virtio- ports is not there, thus causing this bug/failure to start lxd- agent.service. The fix will be to have the package cleanup the old symlinks left in the multi-user.target.wants directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054814 Title: lxd-agent-setup cannot be started on riscv64 6.5.0-9-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd-agent-loader/+bug/2054814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
