Project

General

Custom queries

Profile

Actions
Copy link

Bug #14315

closed

Discovery should no longer use Proxy::Log directly

Added by Stephen Benjamin about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Image
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman-discovery-image/pull/70
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

https://github.com/theforeman/foreman-discovery-image/blob/master/root/usr/lib64/ruby/vendor_ruby/discovery.rb#L34

Related issues 2 (0 open — 2 closed)

Related to Smart Proxy - Bug #12295: Smart proxy stops listening on HTTPS port after log rotateClosed10/23/2015Actions
Related to Discovery - Bug #12641: Refresh facts errors and adds new entry mac000000000000ClosedLukas Zapletal12/01/2015Actions
Actions
Copy link
 #4

Updated by Lukas Zapletal about 9 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).

Actions
Copy link
 #6

Updated by Anonymous about 9 years ago

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

Also available in: Atom PDF