You don't agree HA should check make sure that the storage and disks are available before migrating a VM config to a new host ?
Couldn't stop myself from registering just to reply to this thread.
Despite being a very stubborn and hardliner kind of Linux user for 15+ years and a hardcore fan of Proxmox, I notice the stubbornness and silly argument of these respectable members not accepting a simple "bug" (yeah it is a bug, no matter how 'expert-looking' arguments you bring in) as bug.
I understand that the devs may never be looking at these forums (or likely rarely, if ever), but this kind of attitude stops us hardliners to see a product from an end-user's perspective to make it actually likable by those who just want to 'USE' it, not become an expert 'Nerd' in it.
There can be multiple situations where HA can be useful with local storage, and there can be infinite scenarios where a user can simply make a mistake while creating a VM - remember Proxmox boasts of supporting large enterprise, not just a 4-vm home lab. It's easy to make a dozen such mistakes everyday in a busy workplace, and if you disagree it's obvious you've never worked in a busy place.
Within Proxmox itself there are such checks in places, for example minimum RAM amount can't be more than maximum assigned - the form simply doesn't allow you to make that mistake. This kind of validation is a very BASIC need of all sorts of automation and programming.
Not just NOT having such validation is unacceptable, making a user stuck in situation like NomadCF without easy revert-back options, making them resort to nerdy commandline stuff is simply a Deal-Breaker for ANY ENTERPRISE looking for production ready solution.
And this is coming from someone who just hates UI, loves CLI for almost everything (I've even integrated DRBD manually and run it successfully for 1+ year in Proxmox, just 2 years ago). But I also happen to have accepted the fact that in a Production environment where lots of people, team members or clients depend on you, you just need to get the job done asap. Not dive into fancy research and troubleshooting for a simple mistake like checking a wrong box.
And in my case, it was not even a mistake. It was just a matter of me being 'in-progress' of my infra setup, and the connectivity of one node accidentally lost just for a couple minutes because of the network guys working in parallel on some stuff.
What NomadCF said is actually a very fundamental thing called "Common Sense" - don't step without looking whether there is a ground beneath.
