Bug 1488361

Summary:	[3.5] "when statements should not include jinja2 templating delimiters" warning is shown when running installer with ansible-2.3.1.0-3.el7.noarch
Product:	OpenShift Container Platform	Reporter:	Johnny Liu <jialiu>
Component:	Installer	Assignee:	Russell Teague <rteague>
Installer sub component:	openshift-ansible	QA Contact:	Johnny Liu <jialiu>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	medium	CC:	aos-bugs, jokerman, mmccomas, rteague
Version:	3.5.1
Target Milestone:	---
Target Release:	3.5.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	With Ansible 2.3 warnings are issued when using Jinja delimiters in 'when' conditions. The delimiters have been removed from the code base to avoid these warnings.	Story Points:	---
Clone Of:	1480129	Environment:
Last Closed:	2017-10-17 11:45:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1480129, 1488363
Bug Blocks:	1488359, 1488360

Description Johnny Liu 2017-09-05 08:22:26 UTC

+++ This bug was initially created as a clone of Bug #1480129 +++

Description of problem:
When running 3.2 installer with ansible 2.3, a lot of warning is shown up, though it is harmless.


PLAY [Populate config host groups] *********************************************

TASK [fail] ********************************************************************
Thursday 10 August 2017  02:13:09 +0000 (0:00:00.047)       0:00:00.316 ******* 
 [WARNING]: when statements should not include jinja2 templating delimiters
such as {{ }} or {% %}. Found: {{ g_etcd_hosts is not defined }}

Pls search "when statements should not include jinja2 templating delimiters" keyword in the attached installation log to find more.


Version-Release number of the following components:
ansible-2.3.1.0-3.el7.noarch
openshift-ansible-3.2.63-1.git.0.a21de5e.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
a lot of warning is shown after switch ansible version from 2.2 to 2.3

Expected results:
No more warning.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag


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

--- Additional comment from Johnny Liu on 2017-08-10 05:13 EDT ---



--- Additional comment from Johnny Liu on 2017-08-10 05:59:16 EDT ---

Other version of installer (3.3 ~ 3.6) also has such issues, but the occurrence is less than 3.2.

--- Additional comment from Russell Teague on 2017-08-24 20:21:25 EDT ---

Proposed: https://github.com/openshift/openshift-ansible/pull/5207

--- Additional comment from Russell Teague on 2017-08-29 13:12:14 EDT ---

Merged: https://github.com/openshift/openshift-ansible/pull/5207

Comment 1 Russell Teague 2017-09-05 12:34:40 UTC

Merged: https://github.com/openshift/openshift-ansible/pull/5217

Comment 3 Johnny Liu 2017-09-07 07:32:39 UTC

Waiting for newer errata puddle to include the fix.

Comment 4 Johnny Liu 2017-09-11 07:06:56 UTC

Due no AtomicOpenShift-errata puddle including the fix, switch to AtomicOpenShift puddle to do verification.

Verified this bug with openshift-ansible-3.5.124-1.git.0.d9641fe.el7.noarch, and PASS.

No warning is shown now.

Comment 5 Johnny Liu 2017-09-15 01:42:27 UTC

No openshift-ansible build is attached to errata, no errata puddle, move it to "MODIFIED"

Comment 7 Johnny Liu 2017-09-19 03:53:19 UTC

Verified this bug with openshift-ansible-3.5.125-1.git.0.1c43b24.el7, and PASS.

No warning is seen now.

Comment 9 errata-xmlrpc 2017-10-17 11:45:24 UTC

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-2017:2900