+++ This bug was initially created as a clone of Bug #1564180 +++ Description of problem: Version-Release number of the following components: rpm -q openshift-ansible >>> openshift-ansible-3.7.42-1.git.0.427f18c.el7.noarch rpm -q ansible >>> ansible-2.4.1.0-1.el7.noarch ansible --version >>> ansible 2.4.1.0 config file = /etc/ansible/ansible.cfg configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, May 3 2017, 07:55:04) [GCC 4.8.5 20150623 (Red Hat 4.8.5-14)] How reproducible: Always Steps to Reproduce: 1. Upgrade the rpms to v3.7.42 2. ansible-playbook -i <ansible_hosts_file> /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade.yml Actual results: TASK [Upgrade master packages] ****************************************************************************************************************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TemplateRuntimeError: no test named 'equalto' fatal: [master.ocp.io]: FAILED! => {"failed": true, "msg": "Unexpected failure during module execution.", "stdout": ""} to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_7/upgrade.retry Expected results: Upgrade is successful Additional info: Please attach logs from ansible-playbook with the -vvv flag --- Additional comment from Scott Dodson on 2018-04-05 10:59:30 EDT --- Fixed in https://github.com/openshift/openshift-ansible/pull/7747
Fixed in https://github.com/openshift/openshift-ansible/pull/7775 which is testable in https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=670154
Reproducer: 1) Install 3.6 2) Run control plane and node upgrade playbooks from latest 3.6 shipped versions, this should fail with the error above 3) Update your playbooks to the package referenced in comment 3, re-run, this should work
Upon further review it looks as if this hasn't actually shipped. The problem was introduced in openshift-ansible-3.6.173.0.111-1 so we just need to make sure that we produce a new build before shipping the 3.6 errata.
Reproduced the issue with: openshift-ansible-3.6.173.0.112-1.git.0.b920505.el7.noarch.rpm Verified upgrade runs successfully with: openshift-ansible-3.6.173.0.112-1.git.2.17a27d3.el7.noarch