Bug 1490268
Summary: | [3.7] "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> |
Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.7.0 | CC: | aos-bugs, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | 3.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-ansible-3.7.0-0.126.4 | 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: | Environment: | ||
Last Closed: | 2017-11-28 22:09:56 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: |
Description
Johnny Liu
2017-09-11 08:04:46 UTC
The error is being reported because a variable is being defined which contains Jinja2 templating delimiters. Testing a workaround. This particular use case is fixed[1] in Ansible v2.4.0.0-0.1.rc1 [1] https://github.com/ansible/ansible/commit/23324bdda015256f90737ae93351d0ce71da01b2 Re-test this bug with openshift-ansible-3.7.0-0.126.1.git.0.0bb5b0c.el7.noarch, but failed. Still reproduce the above warning. After checking the code, seem like the PR is not merged into rpm package. $ git tag --contains a77f2ffdd0b1f37de2877a63511d8682ab4362bc openshift-ansible-3.7.0-0.126.2 openshift-ansible-3.7.0-0.126.3 Waiting for build openshift-ansible-3.7.0-0.126.3 Verified this bug with openshift-ansible-3.7.0-0.126.4.git.0.3fc2b9b.el7.noarch, and PASS. No warning is seen now. 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/RHSA-2017:3188 |