Description of problem: cluster-api controller fails to perform deletion of a running VM. the VM has to be stopped first. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. scaledown the machineset 2. worker is not deleted from the ovirt engine. Actual results: Expected results: Additional info:
yes, it's for the default existing machine set, did you try to scale down to 0 workers? what happens if you scale down from 3 to 2 workers?
if I scale from 3 to 2 workers it's working fine
after verifying with Evgeny this is the correct behavior. when scale down the default machineset to 0, the last worker can't delete it because there is no other machineset to move all running pods.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069