Option "Destroy associated VM on host delete" should be disabled by default.
Description of problem:
This is really important, some times we get scenario where some content hosts were removed from vCenter after the customer just remove the CH from Satellite webUI. We already know the warning, however, the customer believes that will be related only to Satellite webUI. This feature is really interesting, however, should be disabled by default and once the customer is aware of how this work, they could switch easily.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure the Compute Resource
2. Create a new VM
3. Delete the CH via Satellite webUI
The machine will be removed from vCenter (or external virtualization resource)
Remove only from Satellite side (db, webUI)
Fixes #30247 - do not delete VMs by default
We've seen multiple users deleting their VMs when they deleted host in
Foreman. That still seems to be very unexpected especially in case of
unmanaged hosts. It's safer to keep the VM and delete it only if users
explicitly want to.
This changes the default behavior and we'll need to cover that in
release notes. However it probably causes less pain than having VMs
running and consuming resources, when people forget to destroy them.