Project

General

Profile

Bug #10477

The foreman-tasks output should be logged into /var/log/foreman/ instead of /usr/share/foreman/tmp/pids/dynflow_executor.output

Added by Bryan Kearney about 6 years ago. Updated almost 6 years ago.

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

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1194607
Description of problem:
The foreman-tasks output should be logged into /var/log/foreman/ instead of /usr/share/foreman/tmp/pids/dynflow_executor.output. There might be very useful logs for debugging that don't get anywhere else and are not collected by the foreman-debug script. Putting it into the right location (+ adding to foreman-debug) should help

Associated revisions

Revision 967db9ab (diff)
Added by Ivan Necas almost 6 years ago

Fixes #10477 - log the dynflow output to proper directory

Use log directory instead of the tmp/pids, that the daemons use by default

Revision d51bc934
Added by Ivan Necas almost 6 years ago

Merge pull request #124 from iNecas/issues/10477

Fixes #10477 - log the dynflow output to proper directory

History

#1 Updated by The Foreman Bot almost 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-tasks/pull/124 added
  • Pull request deleted ()

#2 Updated by Ivan Necas almost 6 years ago

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

Also available in: Atom PDF