+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1489888 +++ ====================================================================== Description of problem: variable cores in profile should correspond with "Total Virtual CPUs" not with Cores per Virtual Socket when user has template with Total Virtual CPUs 4 and he set cores to 2, he will get VM with 8 Virtual CPUs. If user has only hosts with 4 cores, then role will fail with internal filter error (not enough CPUs) Version-Release number of selected component (if applicable): ovirt-ansible-roles-1.0.2-1.el7ev.noarch ansible-2.3.1.0-3.el7.noarch (Originally by Petr Kubica)
As stated in ovirt_vms module documentation[1] cpu_cores correspond to number of cores and cpu_sockets correspond to number of sockets. There is not total virtual CPU parameter. So as part of this bug we will add cpu_sockets paramter to the ovirt-vm-infra role, which will be mapped to cpu_sockets parameter in ovirt_vms Ansible module. [1] http://docs.ansible.com/ansible/latest/ovirt_vms_module.html (Originally by Ondra Machacek)
Verified in ansible-2.3.2.0-2.el7.noarch ovirt-ansible-roles-1.0.4-1.el7ev.noarch
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-2017:3137