Project

General

Profile

Bug #26039

Templates are getting rendered in production.log

Added by Lukas Zapletal 6 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Category:
Logging
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1676302

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.

This was introduced some time ago, but this might be security problem as templates contain sensitive data. Let's fix this.


Related issues

Related to Foreman - Feature #22493: Add new logging options to integrate with logging-journald gemClosed2018-02-02

Associated revisions

Revision d83d1ec0 (diff)
Added by Lukas Zapletal 6 months ago

Fixes #26039 - disable blob logger by default

History

#1 Updated by The Foreman Bot 6 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6479 added

#2 Updated by Tomer Brisker 6 months ago

  • Related to Feature #22493: Add new logging options to integrate with logging-journald gem added

#3 Updated by Marek Hulán 6 months ago

  • Subject changed from Templates are getting rendered in production.log to Templates are getting rendered in production.log

This was in fact asked for. I don't see it as a bug. We use blob logger for this which can be disabled if the log size is too big. We can disable blob logger by default, but should clearly document how to enable it or how to configure journal so it's logged to separate logger.

#4 Updated by Tomer Brisker 6 months ago

  • Fixed in Releases 1.22.0 added

#5 Updated by Lukas Zapletal 6 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF