Bug 1194352
Summary: | Stop truncating backtraces | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Jan Pazdziora <jpazdziora> |
Component: | Usability | Assignee: | Ivan Necas <inecas> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.8 | CC: | bbuckingham, bkearney, cwelton, inecas, sthirugn |
Target Milestone: | Unspecified | Keywords: | 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: | |
Embargoed: |
Description
Jan Pazdziora
2015-02-19 15:52:39 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. Created redmine issue http://projects.theforeman.org/issues/10713 from this bug Proposed fix https://github.com/theforeman/foreman/pull/2438 Merged in upstream, will be part of Foreman 1.9 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 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 Verified in Satellite 6.2 Beta Snap 9 Compose 2. A full backtrace is now provided in the Errors tab of tasks with errors. 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 |