Project

General

Profile

Actions

Bug #10713

closed

Stop truncating backtraces

Added by Ivan Necas over 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Logging
Target version:
Difficulty:
Triaged:
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 1 (0 open1 closed)

Has duplicate Foreman - Bug #7258: Propagate backtraces in our orchestration codeClosed08/26/2014Actions
Actions

Also available in: Atom PDF