Bug 1676302 - Templates are getting rendered in production.log
Summary: Templates are getting rendered in production.log
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Logging
Version: 6.5.0
Hardware: x86_64
OS: Linux
Target Milestone: 6.6.0
Assignee: Lukas Zapletal
QA Contact: Stephen Wadeley
: 1705963 (view as bug list)
Depends On:
Blocks: Red Hat1122832
TreeView+ depends on / blocked
Reported: 2019-02-11 22:47 UTC by Suraj Patil
Modified: 2020-06-29 16:34 UTC (History)
3 users (show)

Fixed In Version: foreman-1.22.0-0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-10-22 19:52:09 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26039 0 Normal Closed Templates are getting rendered in production.log 2020-06-29 16:27:02 UTC

Description Suraj Patil 2019-02-11 22:47:44 UTC
Description of problem:

When we build the host all the templates are rendered and outputted to /var/log/production.log. because of this production.log size grows high.

Version-Release number of selected component (if applicable):
Satellite 6.5 snap 15.0

How reproducible:
Create new host and monitor production.log 

Actual results:
Logs rendered templates to production.log

Expected results:
Should not log the rendered templates

Additional info:

Logging in /etc/foreman/settings.yaml is set to info.

Comment 3 Lukas Zapletal 2019-02-12 15:09:17 UTC
Created redmine issue https://projects.theforeman.org/issues/26039 from this bug

Comment 5 Bryan Kearney 2019-03-05 15:04:41 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26039 has been resolved.

Comment 6 Oliver Falk 2019-05-17 09:07:58 UTC
*** Bug 1705963 has been marked as a duplicate of this bug. ***

Comment 9 Lukas Zapletal 2019-05-22 12:30:07 UTC
The change is in the codebase, default value is there. Just try it and see yourself if it really work. Yaml example is not being deployed by our installer.

Comment 13 Bryan Kearney 2019-10-22 19:52:09 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.


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