Is there an existing issue for this?

• There is no existing issue for this bug

Is this happening on an up to date version of Incus?

• This is happening on a supported version of Incus

Incus system details

6.22

Instance details

incus info name --project correct-project
Name: name
Description:
Status: RUNNING
Type: virtual-machine
Architecture: x86_64
PID: 1199492
Created: 2026/03/13 04:48 EET
Last Used: 2026/03/13 04:54 EET
Started: 2026/03/13 04:54 EET

Operating System:
OS: Debian GNU/Linux
OS Version: 13
Kernel Version: 6.12.63+deb13-amd64
Hostname: name
FQDN: localhost

Resources:
Processes: 16
CPU usage:
CPU usage (in seconds): 318
Memory usage:
Memory (current): 1.09GiB
Network usage:
enp5s0:
Type: broadcast
State: UP
Host interface: ...
MAC address: ...
MTU: 1500
Bytes received: 425.20MB
Bytes sent: 76.01MB
Packets received: 6412010
Packets sent: 416225
IP addresses:
inet: ... (global)
inet6: ... (global)
inet6: ... (global)
inet6: ... (link)
lo:
Type: loopback
State: UP
MTU: 65536
Bytes received: 398.08kB
Bytes sent: 398.08kB
Packets received: 4920
Packets sent: 4920
IP addresses:
inet: 127.0.0.1/8 (local)
inet6: ::1/128 (local)

Instance log

No response

Current behavior

I had a vm in the default project on default dir storage

First I moved it to another project and another storage pool
incus move name name --target-project wrong-project --storage wrong-pool
and then to the correct one
incus move name name --project wrong-project --target-project correct-project --storage default

Now I try to list all my volumes, but I get

incus storage volume list default --all-projects -c etnUc
Error: Failed to fetch instance "name" in project "default": Instance not found

and

incus storage volume delete default virtual-machine/name --project default
Error: Storage pool volume not found

The instance is happily running in the correct project, though

Expected behavior

Listing should succeed
Should be able to delete stale/corrupted data

Steps to reproduce

Don't have any