Not able to create new cluster because of VMID conflicts #28
Description
I have managed to get the proxmox provider into a faulty state, where it can´t destroy or create a new cluster.
If you have a running cluster, then delete the nodes/worker from inside Proxmox and afterwards tries to delete the same nodes or destroying the cluster from Omni. You will see the provider is looking for file <vmid>.conf, which it can´t find because the VM was deleted and therefore not able to destroy the cluster and perform a clean up - does not look like the destroy function has any timeout function.
At the same time, if you create a new cluster through omni. The provider will use the first available VMID for the new node which is fine. But that VMID is also the exact VMID the old cluster is looking for. So when the new node gets created, the old cluster will delete it and will be missing in the new cluster - and the provider does not have any retry feature for making the node again.