Bug 2069685 - UI crashes on load if a pinned resource model does not exist
Summary: UI crashes on load if a pinned resource model does not exist
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Jeff Phillips
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-03-29 13:21 UTC by Jeff Phillips
Modified: 2022-08-10 11:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:02:32 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11249 0 None open Bug 2069685: Fix UI crash when pinned resource model does not exist 2022-03-30 12:56:38 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:02:50 UTC

Description Jeff Phillips 2022-03-29 13:21:53 UTC
Description of problem:

If a user has pinned a resource type that is no longer supported on the cluster, the UI crashes on load of the developer perspective.

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

How reproducible:


Steps to Reproduce:
1. Pin a CRD type that is created by an operator (KFDef on a system with RHODS)
2. Login to another system without RHODS using the same browser

Actual results:

UI crashes

Expected results:

UI shows but without the pinned resource that doesn't exist

Additional info:

Comment 3 Christoph Jerolimov 2022-04-25 09:14:53 UTC
Pinning, unpinning, reorder works fine. Could not reproduce a crash when uninstall an operator, this might happen just locally, so setting this to verified as I don't see an issue anymore.


Comment 6 errata-xmlrpc 2022-08-10 11:02:32 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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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.


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