Bug #14315
Discovery should no longer use Proxy::Log directly
Difficulty:
Triaged:
No
Related issues
Associated revisions
History
#1
Updated by Stephen Benjamin about 7 years ago
- Related to Bug #12295: Smart proxy stops listening on HTTPS port after log rotate added
#2
Updated by Stephen Benjamin about 7 years ago
- Subject changed from Discovery should no longer use Proxy::Logger directly to Discovery should no longer use Proxy::Log directly
#3
Updated by Lukas Zapletal about 7 years ago
- Related to Bug #12641: Refresh facts errors and adds new entry mac000000000000 added
#4
Updated by Lukas Zapletal about 7 years ago
This was a problem when refresh_fact API is called via Proxy, it calls Facter which calls custom facter code which uses some helper methods defined in discovery.rb. They send some debug/info logs into syslog (which was already opened by Proxy itself as this was a sub-process).
#5
Updated by The Foreman Bot about 7 years ago
- Status changed from New to Ready For Testing
- Assignee set to Lukas Zapletal
- Pull request https://github.com/theforeman/foreman-discovery-image/pull/70 added
#6
Updated by Anonymous almost 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman-discovery-image|c4631779758166409e567b334aca8ea23ffbc098.
Fixes #14315 - fixed proxy logger and enabled log buffer