Bug 2028885

Summary: Console should show an error context if it logs an error object
Product: OpenShift Container Platform Reporter: Christoph Jerolimov <cjerolim>
Component: Dev ConsoleAssignee: Christoph Jerolimov <cjerolim>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: low Docs Contact:
Priority: low    
Version: 4.10CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:31:36 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 Christoph Jerolimov 2021-12-03 16:45:01 UTC
Description of problem:
As an developer of OCP/ODC, and also as user which opens the browser console I see sometimes errors which are logged without any context. Errors should show at least a short info why/where they happen.

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

How reproducible:
Only when an error occours

Steps to Reproduce:
1. Open developer console
2. Open browser console
3. Produce an error

Actual results:
Not all errors logs a context

Expected results:
Errors should log a message to identify which code area logs an error

Additional info:

Comment 2 Christoph Jerolimov 2021-12-20 11:19:19 UTC
This change only adds new logging information to the browser console when an error appears.

Checked the browser console log on 4.10.0-0.nightly-2021-12-16-185411 and it looks fine.

Comment 6 errata-xmlrpc 2022-03-10 16:31:36 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056