How to delete VMs in the unknown state

The platform may put VMs into the UNKNOWN state if there is an issue with a connection to the hypervisor. It marks these VMs with the gray UNKNOWN state label. 

If the platform later recovers the connection to the hypervisor, it will restore the VMs to their corresponding state.

A user may see a VM in an UNKNOWN state and wish to delete it but this action is protected by a privilege because after you delete the VM, you may also need to check the host machine.

In addition, if the VM is in another enterprise, you will need the privilege to Allow user to switch enterprise or you will need to log in to the enterprise.

If you do not check the hypervisor after deleting the VM in the platform, the VM may remain in the hypervisor without being registered in the platform. If the information in the platform and in the hypervisor are not consistent, then this may lead to errors or problems.

For example, if the user deletes a persistent VM in an unknown state, then the persistent template will be available to the user. If the user deploys the VM again, then this would create another VM on the hypervisor using the same external disks as the original VM.

This feature improves platform stability by enabling greater control over situations such as minor communication failures between the hypervisor and the platform.