Sometimes, a VM stays in “pending” mode forever because of a bug in OpenNebula, the cloud management software for the HPC Cloud.
This only affects VMs with a “VNC console” attached, because it is a bug with the network port allocation needed to connect to the VNC console.
If you do not need direct console access to your VM, but can work over an SSH connection, we advise to remove the VNC console from the template for your VM.
Detection is somewhat difficult. When your VM stays pending without an obvious cause, the VNC port problem may be the cause.
First of all, check that your VM has a VNC console attached. Without a VNC console, the problem cannot occur.
This will prevent future VMs from using a VNC console.
Here is how to remove the VNC console from a pending VM:
The VM should begin deploying, but without a VNC console.
You may or may not have the permission to “Hold” the deployment of a VM. If you do, this is a way to try and make the VM work while keeping the VNC console.
This will assign a different VNC port to the VM and, with some luck, this new port does not have the problem.