After fiddling around for several hours, I eventually discovered a workaround here.
Looking at the VM delete workaround I used which came from here:
onedb update-body vm --id 255
Remove the tag IMPORTED
onevm recover --delete-db 255
Removal of the IMPORTED tag means that ‘–delete-db’ leaves behind a record in the the vm_import table which in turn prevents the VM from ever appearing as a wild.
To fix, I had to run the the following from the DB:
MariaDB [opennebula]> delete from vm_import where vmid = ‘255’;
Colm