After migration, VM is still registered on SolusVM 2 source compute resource

Symptoms 

After migration VM is still registered on SolusVM 2 source compute resource

Cause

Unknown

Resolution

Change CR for affected VPS:

1. Create SolusVM 2 database backup: How to create SolusVM 2 database backup?
2. Access the database: How to access SolusVM 2 database?
3. Update ID of CR, ID of Storage (both are taken from SolusVM 2 web interface), and VNC port for VNC console (taken from virsh edit b523c082-4e43-422a-a0e9-7408a598ad23 on target node:

# update compute_resource_vms set compute_resource_id=7 where id=83;

# update compute_resource_vms set storage_id=12 where id=83;

# update compute_resource_vms set settings=settings||'{"vnc": {"port": 5912, "password": "Vl2ttYWH"}}' where id=83;