Project

General

Profile

Bug #10713

Stop truncating backtraces

Added by Ivan Necas over 5 years ago. Updated about 2 years ago.

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

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1194352
Description of problem:

In the rare case when an error happens in code which is not foreman's, WebUI only shows very few lines of backtrace, even if the problem is in katello or dynflow. The backtrace should not claim it shows "Full trace" if it does not.

Version-Release number of selected component (if applicable):

Satellite 6.0.8

How reproducible:

Deterministic.

Steps to Reproduce:
1. Have situation when application fails in katello.
2. Check the backtrace shown on the "Oops, we're sorry but something went wrong" page.

Actual results:

Just backtrace from foreman, it seems.

Expected results:

Complete backtrace.

Additional info:

Alternatively, the page should point the user to the whole backtrace to be found in /var/log/foreman/production.log.


Related issues

Has duplicate Foreman - Bug #7258: Propagate backtraces in our orchestration codeClosed2014-08-26

Associated revisions

Revision 01e78260 (diff)
Added by Ivan Necas over 5 years ago

Fixes #10713 - improved backtrace logging

  • full trace in 500 page in production shows really the full trace
  • Foreman::Logging.exception as an unified entry point for exceptions logging
  • the backtrace cleaner doesn't delete the plugins
  • the orchestration exceptions gets the backtrace covered by logger
  • some generic resuced exceptions get covered by logger

History

#1 Updated by Ivan Necas over 5 years ago

  • Status changed from New to Assigned
  • Assignee set to Ivan Necas

#2 Updated by The Foreman Bot over 5 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2438 added
  • Pull request deleted ()

#3 Updated by Dominic Cleal over 5 years ago

  • Category set to Logging
  • Legacy Backlogs Release (now unused) set to 35

#4 Updated by Ivan Necas over 5 years ago

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

#5 Updated by Dominic Cleal over 5 years ago

  • Has duplicate Bug #7258: Propagate backtraces in our orchestration code added

Also available in: Atom PDF