Description of problem: TASK [ovirt-manageiq : Deploy the qcow image to oVirt engine] ***************************************************************************************************************************************************** fatal: [engine]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'disk_storage_domain' is undefined\n\nThe error appears to have been in '/usr/share/ansible/roles/oVirt.manageiq/tasks/deploy_qcow2.yml': line 63, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n- block:\n - name: Deploy the qcow image to oVirt engine\n ^ here\n"} Version-Release number of selected component (if applicable): ovirt-ansible-manageiq-1.1.12-0.1.master.20180823081650.el7.noarch How reproducible: always Steps to Reproduce: 1. define miq_vm_disk_storage for deploying qcow to specific domain
tested with: ovirt-ansible-manageiq.noarch 0:1.1.12-0.1.master.20180904110406.el7 still failing but later: ASK [oVirt.manageiq : Add database disk for CFME] ***************************** 15:02:14 task path: /usr/share/ansible/roles/oVirt.manageiq/tasks/cfme_add_disk.yml:1 15:02:14 fatal: [engine]: FAILED! => { "msg": "The task includes an option with an undefined variable. The error was: 'disk_storage_domain' is undefined\n\nThe error appears to have been in '/usr/share/ansible/roles/oVirt.manageiq/tasks/cfme_add_disk.yml': line 1, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Add {{ item }} disk for CFME\n ^ here\nWe could be wrong, but this one looks like it might be an issue with\nmissing quotes. Always quote template expression brackets when they\nstart a value. For instance:\n\n with_items:\n - {{ foo }}\n\nShould be written as:\n\n with_items:\n - \"{{ foo }}\"\n" }
Verified in ovirt-ansible-manageiq-1.1.12-0.1.master.20180907093028.el7.noarch
QE verification bot: the bug was verified upstream
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.