Project

General

Profile

Bug #14315

Discovery should no longer use Proxy::Log directly

Added by Stephen Benjamin over 5 years ago. Updated over 5 years ago.

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


Related issues

Related to Smart Proxy - Bug #12295: Smart proxy stops listening on HTTPS port after log rotateClosed2015-10-23
Related to Discovery - Bug #12641: Refresh facts errors and adds new entry mac000000000000Closed2015-12-01

Associated revisions

Revision c4631779 (diff)
Added by Lukas Zapletal over 5 years ago

Fixes #14315 - fixed proxy logger and enabled log buffer

History

#1 Updated by Stephen Benjamin over 5 years ago

  • Related to Bug #12295: Smart proxy stops listening on HTTPS port after log rotate added

#2 Updated by Stephen Benjamin over 5 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 over 5 years ago

  • Related to Bug #12641: Refresh facts errors and adds new entry mac000000000000 added

#4 Updated by Lukas Zapletal over 5 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 over 5 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 over 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF