Hi,
I’ve recently migrated to an Incus cluster and am loving it. I had a couple of situations where I cancelled a VM move and now I am unable to re-start the move. I receive the following error:
Migration failed on instance NAME
Instance move to destination failed on source: Failed migration on
source: Failed adding migration storage snapshot block device:
Failed adding block device: Duplicate nodes with
node-name='incus_root_snapshot'
Is there any way to get past this?
Regards,
Simon
Welcome!
Incus is complaining about duplicate nodes with the same ‘node-name’.
It looks like there is an issue in the SQLite database of Incus, where it stores the configuration.
You would be able to have a look into there using the incus admin sql command.
You would dump the database (export a copy) and then search for references of node-name and incus_root_snapshot. You can compare the fields between the problematic VM and a good VM.
Once you verify that the problem is indeed in there, the next step is to make a subtle change in the database to fix the problem.
Hmm, looks like the failed move has left the temporary disk overlay device in the config, causing this failure.
Restarting the VM will clear the situation, but it’d be good to understand what led to that situation in the first place. Do you have more details on the initial move failure?
Thanks all. I wasn’t able to find anything in the SQL dump, however a stop/start cleared the problem.
I forgot to mention that this was not just a move, but a live VM migration to another host. There wasn’t anything out of the ordinary that I was doing. I had a couple VM’s that I wanted to test live migrations on. I stopped them, updated the YAML configuration to enable live migration, started them up and then started the move. I cancelled them after seeing how slow the move would take. I tried starting them again later and encountered the error.