Description of problem: In openshift-ansible-filter-plugins-3.7.31-1.git.0.08008d0.el7.noarch.rpm a filter is being called using a new (3.9) name instead of the old (3.7) name yielding this result: TASK [openshift_logging_elasticsearch : template] ****************************************************************************************** Tuesday 27 February 2018 13:07:11 -0500 (0:00:00.208) 0:02:18.664 ****** fatal: [54.164.255.160]: FAILED! => {"msg": "template error while templating string: no filter named 'lib_utils_oo_random_word'. String: {{ 16 | lib_utils_oo_random_word | b64encode }}"} Version-Release number of selected component (if applicable): openshift-ansible-filter-plugins-3.7.31-1.git.0.08008d0.el7.noarch.rpm How reproducible: Always Steps to Reproduce: 1. Install a cluster using openshift-ansible-3.7.31-1.git.0.08008d0 2. 3. Actual results: see above Expected results: logging is deployed correctly Additional info: Description of problem: Version-Release number of the following components: rpm -q openshift-ansible rpm -q ansible ansible --version How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated Expected results: Additional info: Please attach logs from ansible-playbook with the -vvv flag
Change this: logging_user_passwd: "{{ 16 | lib_utils_oo_random_word | b64encode }}" to: logging_user_passwd: "{{ 16 | oo_random_word | b64encode }}" in: roles/openshift_logging_elasticsearch/tasks/main.yaml
This is already fixed in 3.7 branch: eddb211416 (Eric Wolinetz 2018-02-15 17:39:03 -0600 151)
Already in openshift-ansible-3.7.33-1
Pass using openshift3/ose-ansible/images/v3.7.35-1
Can confirm - 3.7.35 doesn't have this problem. Thanks!
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-2018:0636