Description of problem: TASK [ovirt-image-template : Find data domain] ******************************************************************************************************************************************************************** fatal: [**FILTERED**]: FAILED! => {"failed": true, "msg": "You need to install \"jmespath\" prior to running json_query filter"} TASK [ovirt-image-template : Remove vm] *************************************************************************************************************************************************************************** fatal: [**FILTERED**]: FAILED! => {"failed": true, "msg": "The conditional check 'ovirt_templates | length == 0' failed. The error was: error while evaluating conditional (ovirt_templates | length == 0): 'ovirt_templates' is undefined\n\nThe error appears to have been in '/usr/share/ansible/roles/ovirt-image-template/tasks/main.yml': line 104, column 7, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n always:\n - name: Remove vm\n ^ here\n"} missing https://pypi.python.org/pypi/jmespath-terminal/0.2.1 install it solve this issue Version-Release number of selected component (if applicable): ansible-2.3.1.0-3.el7.noarch ovirt-ansible-roles-1.0.1-1.el7ev.noarch python-ovirt-engine-sdk4-4.1.6-1.el7ev.x86_64 ovirt-engine-restapi-4.1.5.2-0.1.el7.noarch ovirt-engine-4.1.5.2-0.1.el7.noarch
Petr, could you please create also github issue and reference it here?
Ansible package itself should contain dependency on python2-jmespath packages itself as mentioned in BZ1465586 and BZ1484910, so we need to wait until downstream ansible package is fixed
Moving back to new, as adding python-jmespath as dependency to ovirt-ansible-roles is a termporary fix, which should be removed when BZ1484910 is fixed properly (ansible package itself should depend on python-jmespath)
(In reply to Martin Perina from comment #4) > Moving back to new, as adding python-jmespath as dependency to > ovirt-ansible-roles is a termporary fix, which should be removed when > BZ1484910 is fixed properly (ansible package itself should depend on > python-jmespath) I am working on it, but it is not just a matter of making ansible depend on python-jmespath - there is no python-jmespath package in RHEL, so we need to add it. BZ1489592. Where are you taking it from?
(In reply to Pavel Cahyna from comment #5) > (In reply to Martin Perina from comment #4) > > Moving back to new, as adding python-jmespath as dependency to > > ovirt-ansible-roles is a termporary fix, which should be removed when > > BZ1484910 is fixed properly (ansible package itself should depend on > > python-jmespath) > > I am working on it, but it is not just a matter of making ansible depend on > python-jmespath - there is no python-jmespath package in RHEL, so we need to > add it. BZ1489592. Where are you taking it from? Here's the build [1] and errata [2], we needed to tag the package into RHVM management channel and the dependency to ovirt-ansible-roles package [4] to fix that issue until it's properly fixed in ansible package. This is the same version of the packages which is used for upstream Ansible package [3] [1] https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=512255 [2] https://errata.devel.redhat.com/advisory/30173 [3] https://cbs.centos.org/koji/buildinfo?buildID=19255 [4] https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=593830
I quickly looked at your erratum and see a glitch: it uses the build python-jmespath-0.9.0-5.el7ost (the OpenStack one), which produces a python-jmespath binary package, but the erratum synopsis and topic refer to python2-jmespath. This package is produced by the OpenShift version (https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=515839). I chose the EPEL version for inclusion into RHEL Extras btw., which corresponds to the OpenShift one, not to the OpenStack one. BTW. what information do you need from me?
bz1484910 is fixed, can this bug be closed?
BTW why is there needinfo? on me?
(In reply to Pavel Cahyna from comment #9) > BTW why is there needinfo? on me? Just to be sure you to notice the comment :-) Moving to MODIFIED, thanks!
Verified in python-jmespath-0.9.0-5.el7ost.noarch ovirt-ansible-vm-infra-1.1.3-1.el7ev.noarch ansible-2.4.1.0-1.el7ae.noarch ovirt-ansible-infra-1.1.2-1.el7ev.noarch ovirt-ansible-image-template-1.1.3-1.el7ev.noarch ovirt-ansible-cluster-upgrade-1.1.3-1.el7ev.noarch ovirt-ansible-roles-1.1.2-1.el7ev.noarch ovirt-ansible-manageiq-1.1.3-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-2018:1534
BZ<2>Jira Resync