Bug 2040296 - Layout issue on "Something went wrong" page
Summary: Layout issue on "Something went wrong" page
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.z
Assignee: Jakub Hadvig
QA Contact: Siva Reddy
Depends On: 2002007
TreeView+ depends on / blocked
Reported: 2022-01-13 11:48 UTC by Christoph Jerolimov
Modified: 2022-02-14 12:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-02-14 12:00:47 UTC
Target Upstream Version:

Attachments (Terms of Use)
Namespace no error (197.14 KB, image/png)
2022-02-09 00:51 UTC, Siva Reddy
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 10072 0 None open [release-4.9] Bug 2040296: Enable error stack trace messages to scroll 2022-01-13 11:50:20 UTC
Red Hat Product Errata RHBA-2022:0488 0 None None None 2022-02-14 12:01:00 UTC

Description Christoph Jerolimov 2022-01-13 11:48:27 UTC
This bug was initially created as a copy of Bug #2002007

I am copying this bug because: 

The pre blocks containing error details and stack traces overlap each other on the error boundary "Something went wrong" page (see screenshot), perhaps related to PatternFly changes or removing Bootstrap.

Comment 2 Siva Reddy 2022-02-09 00:51:11 UTC
Created attachment 1859943 [details]
Namespace no error

Cluster version:

Steps to verify:
1. Login OCP, and navigate to Administration -> Namespaces page
         Now page loads correctly, the user can check the list of the namespaces, no error shown on the page

Comment 5 errata-xmlrpc 2022-02-14 12:00: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 (OpenShift Container Platform 4.9.21 bug fix 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.


Note You need to log in before you can comment on or make changes to this bug.