Description of problem: When using the ovirt.vm-infra module is not possible to set a custom serial to a VM nor to specify the desired serial-policy That feature is provided by ovirt-vm [0] Version-Release number of selected component (if applicable): ovirt-ansible-vm-infra-1.1.14-1 Steps to Reproduce: a playbook example with the expected behaviour [...] vars: vm_custom_serial: state: running cluster: Minion serial_policy: custom serial_policy_value: my_personal_custom_serial vms: - name: serial1 profile: "{{ vm_custom_serial }}" - name: serial2 serial_policy_value: my_personal_custom_serial_just_for_2 profile: "{{ vm_custom_serial }}" - name: serial3 profile: "{{ vm_custom_serial }}" roles: - ovirt.vm-infra Actual results: Nothing is changed on VMs serial1, serial2 and serial3 Expected results: A custom serial number is set on those 3 VMs [0] https://docs.ansible.com/ansible/latest/modules/ovirt_vm_module.html#ovirt-vm-module
verified in ovirt-ansible-vm-infra-1.1.15-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/RHEA-2019:1564
sync2jira