Project

General

Profile

Actions
Copy link

Feature #3394

closed

Run puppet with --trace

Added by Dominic Cleal about 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Target version:
1.4.0
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 2 (0 open — 2 closed)

Related to Installer - Feature #3435: foreman-installer fails when /etc/hosts is not filled appropriatelyResolved10/21/2013Actions
Related to Kafo - Bug #30505: Do not display puppet traceback when reporting errorsClosedEric HelmsActions
Actions
Copy link
 #1

Updated by Dominic Cleal about 11 years ago

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

Updated by Lukas Zapletal almost 11 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Lukas Zapletal
  • Target version set to 1.9.3
  • Translation missing: en.field_release set to 2
  • Difficulty set to easy
Actions
Copy link
 #3

Updated by Anonymous almost 11 years ago

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

Updated by Ewoud Kohl van Wijngaarden over 4 years ago

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

Also available in: Atom PDF