Closed candlerb closed 5 months ago
For comparison, on an Ubuntu 22.04 box which successfully upgraded:
root@nuc3:~# ls -l /etc/systemd/system/incus*
ls: cannot access '/etc/systemd/system/incus*': No such file or directory
root@nuc3:~# ls -l /lib/systemd/system/incus*
-rw-r--r-- 1 root root 532 Mar 26 16:36 /lib/systemd/system/incus-lxcfs.service
-rw-r--r-- 1 root root 641 Mar 26 16:36 /lib/systemd/system/incus.service
-rw-r--r-- 1 root root 195 Mar 26 16:36 /lib/systemd/system/incus.socket
-rw-r--r-- 1 root root 323 Mar 26 16:36 /lib/systemd/system/incus-startup.service
-rw-r--r-- 1 root root 260 Mar 26 16:36 /lib/systemd/system/incus-user.service
-rw-r--r-- 1 root root 204 Mar 26 16:36 /lib/systemd/system/incus-user.socket
root@nuc3:~# ls -l /opt/incus/lib/systemd/
total 12
-rwxr-xr-x 1 root root 385 Mar 26 16:36 incusd
-rwxr-xr-x 1 root root 488 Mar 26 16:36 incus-startup
-rwxr-xr-x 1 root root 115 Mar 26 16:36 incus-user
A fix has already been merged in the packaging branch and we're just waiting for it to finish building.
This trips on some systems that for some reason had a symlink at /etc/systemd/system/incus.service
. You can remove that symlink and try the update again to unblock things.
That fixes it, thank you:
root@nuc1:~# rm /etc/systemd/system/incus.service
root@nuc1:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up incus-base (0.7-202403261638-ubuntu20.04) ...
Setting up incus (0.7-202403261638-ubuntu20.04) ...
Setting up incus-ui-canonical (0.7-202403261638-ubuntu20.04) ...
Processing triggers for libc-bin (2.31-0ubuntu9.14) ...
root@nuc1:~#
I'll leave the other machine until the updates are published, to give it a proper test.
It's being published now should hit the package mirror in the next 5min or so.
Attempting to update an Ubuntu 20.04 server:
Oops. Investigating:
Is it because of the missing incus.service ?
(this is in red; the symlink target doesn't exist)
I have a second virtually identical box, which I haven't attempted to upgrade yet. It shows there is an incus.service:
(these symlinks are all valid, but note that "incus.service" and "incus-user.service" aren't present in /etc/systemd/system/)
It seems to me that part of the migration of incus.service is broken? I didn't get this issue when upgrading incus on Ubuntu 22.04 servers though.
I can leave nuc1 in broken state if necessary ("incus list" still works anyway), and I will hold off upgrading nuc2 until there's a proper solution to test.