Bug 1468894 - warning message appears when running the metrics setup script regarding jinja2 templating
Summary: warning message appears when running the metrics setup script regarding jinja...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: Generic
Version: 1.0.4.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.0
: 1.1.1
Assignee: Shirly Radco
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks: oVirt-Metrics-and-Logs 1475135
TreeView+ depends on / blocked
 
Reported: 2017-07-09 15:06 UTC by Shirly Radco
Modified: 2017-12-22 08:08 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:07:19 UTC
oVirt Team: Metrics
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 79473 0 master MERGED update jinja2 templates 2017-07-19 06:58:05 UTC

Description Shirly Radco 2017-07-09 15:06:41 UTC
Description of problem:
When running the metrics setup script we get these warnings.

TASK [ovirt_collectd/read_statsd : Allow collectd to listen on statsd port]
[WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: "{{ ansible_selinux.mode }}" in ["enforcing", "permissive"]

TASK [ovirt_collectd/collectd_setup : Set collectd_tcp_network_connect]
[WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: "{{ ansible_selinux.mode }}" in ["enforcing", "permissive"]

We should remove the {{ }} : 

' ansible_selinux.mode  in ["enforcing", "permissive"] '

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Run metrics setup script
2.
3.

Actual results:
There are warnings.

Expected results:
No wornings.

Additional info:

Comment 1 Lukas Svaty 2017-09-21 15:53:17 UTC
verified in ovirt-engine-metrics-1.1.1-0.0.master.20170919065728.el7.centos.noarch

Comment 2 Sandro Bonazzola 2017-12-20 11:07:19 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.