Bug 1676302

Summary:	Templates are getting rendered in production.log
Product:	Red Hat Satellite	Reporter:	Suraj Patil <supatil>
Component:	Logging	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED ERRATA	QA Contact:	Stephen Wadeley <swadeley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	egolov, lzap, ofalk
Target Milestone:	6.6.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	foreman-1.22.0-0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 19:52:09 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:
Bug Blocks:	1122832

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.

https://access.redhat.com/errata/RHSA-2019:3172