Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

Created redmine issue https://projects.theforeman.org/issues/26039 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26039 has been resolved.

*** Bug 1705963 has been marked as a duplicate of this bug. ***

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.

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