Project

General

Profile

Feature #3394

Run puppet with --trace

Added by Dominic Cleal about 9 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

In the case of errors coming from Puppet types, providers etc, it's necessary to run Puppet with --trace to get a stack trace back.

Ideally, we'd always run Puppet with --trace as it's otherwise harmless, but then send the stack traces to the log file for further investigation. Otherwise it could be an argument to the binary.


Related issues

Related to Installer - Feature #3435: foreman-installer fails when /etc/hosts is not filled appropriatelyResolved2013-10-21
Related to Kafo - Bug #30505: Do not display puppet traceback when reporting errorsClosed

Associated revisions

Revision f87b9d41 (diff)
Added by Lukas Zapletal almost 9 years ago

fixes #3394 - added --trace puppet option as default

History

#1 Updated by Dominic Cleal about 9 years ago

  • Related to Feature #3435: foreman-installer fails when /etc/hosts is not filled appropriately added

#2 Updated by Lukas Zapletal almost 9 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Lukas Zapletal
  • Target version set to 1.9.3
  • Legacy Backlogs Release (now unused) set to 2
  • Difficulty set to easy

#3 Updated by Anonymous almost 9 years ago

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

#4 Updated by Ewoud Kohl van Wijngaarden over 2 years ago

  • Related to Bug #30505: Do not display puppet traceback when reporting errors added

Also available in: Atom PDF