Description of problem: ovirt_vm module documentation says about force_migrate this: If true, the VM will migrate even if it is defined as non-migratable. However, according to Andrej Krejcir: This is intended. There are 3 migration modes: - Automatic migration allowed - It is possible to migrate the VM by a script with force_migrate=no - Manual migration only - The force_migrate has to be 'yes'. - Migration not allowed - This mode can be useful for example when the VM uses pass-through of host devices. It looks like a documentation bug. See here: https://bugzilla.redhat.com/show_bug.cgi?id=1721222#c4 If this is indeed the case, the documentation at https://docs.ansible.com/ansible/latest/modules/ovirt_vm_module.html should be changed. Version-Release number of selected component (if applicable): Ansible 2.8 How reproducible: 100 %
Moving to Ansible component, because Ansible module documentation is available only in upstream Ansible doc.
ansible-2.8.3 has been released, please check this bug is fixed there.
Verified on: ansible-2.8.3-1.el7ae.noarch Verification steps: 1. ansible-doc ovirt_vm | grep -A 5 "force_migrate"
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, 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/RHBA-2019:1935