Bug 1194352

Summary: Stop truncating backtraces
Product: Red Hat Satellite Reporter: Jan Pazdziora <jpazdziora>
Component: UsabilityAssignee: Ivan Necas <inecas>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.8CC: bbuckingham, bkearney, cwelton, inecas, sthirugn
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/10713
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 08:48:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jan Pazdziora 2015-02-19 15:52:39 UTC
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.

Comment 1 RHEL Program Management 2015-02-20 00:59:56 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Ivan Necas 2015-06-05 10:12:08 UTC
Created redmine issue http://projects.theforeman.org/issues/10713 from this bug

Comment 4 Ivan Necas 2015-06-05 10:24:02 UTC
Proposed fix https://github.com/theforeman/foreman/pull/2438

Comment 5 Ivan Necas 2015-06-09 15:15:26 UTC
Merged in upstream, will be part of Foreman 1.9

Comment 8 Tazim Kolhar 2016-04-05 04:29:53 UTC
Hi,

   please provide verification steps for :
   1. Have situation when application fails in katello.
   (Can please give example here)
 
   2. Check the backtrace shown on the "Oops, we're sorry but something went    
   wrong" page.

Thanks and Regards,
Tazim

Comment 9 Ivan Necas 2016-04-05 11:21:47 UTC
1. configure the satellite to use external ldap authentication
2. simulate the satellite can't reach the ldap (as simply as upading the /etc/hosts on the machine to use some fake ip for the ldap server
3. try to login

The reqeust should fail, but one should be able to get the backtrace of the error in /var/log/foreman/production.log

Comment 11 jcallaha 2016-04-26 19:24:52 UTC
Verified in Satellite 6.2 Beta Snap 9 Compose 2.

A full backtrace is now provided in the Errors tab of tasks with errors.

Comment 13 errata-xmlrpc 2016-07-27 08:48:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1500