Bug 2111686 - [OKD/nanokube] Different NPE when using console with a nanokube cluster
Summary: [OKD/nanokube] Different NPE when using console with a nanokube cluster
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.12
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.12.0
Assignee: Christoph Jerolimov
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-07-27 20:17 UTC by Christoph Jerolimov
Modified: 2023-01-17 19:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-01-17 19:53:34 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11791 0 None open Bug 2111686: Fix NPE when project or build status is not defined 2022-07-27 20:18:49 UTC
Red Hat Product Errata RHSA-2022:7399 0 None None None 2023-01-17 19:54:01 UTC

Description Christoph Jerolimov 2022-07-27 20:17:10 UTC
Description of problem:
While using the console web UI with a nanokube cluster at our hack week in June 2022, we found different NPEs when the project or build status wasn't set.

Version-Release number of selected component (if applicable):
4.12 (but maybe all)

How reproducible:
Always, but only when running a nanokube cluster

Steps to Reproduce:
1. Clone and build https://github.com/RedHatInsights/nanokube

export KUBEBUILDER_ASSETS=`~/go/bin/setup-envtest use 1.21 -p path`

2. Run our console web UI against this cluster!
# do not call   ./contrib/oc-environment.sh   !!
export BRIDGE_USER_AUTH="disabled"
export BRIDGE_K8S_MODE="off-cluster"
export BRIDGE_K8S_AUTH="bearer-token"
export BRIDGE_K8S_AUTH_BEARER_TOKEN="ignored-by-proxy"

Actual results:
Crashes while navigate to the project list or details page.
Crash on the build config list page.

Expected results:
No crashes, or at least not the described.

Additional info:

Comment 1 Christoph Jerolimov 2022-07-28 14:45:32 UTC
Had this crash now also on a normal OpenShift cluster!

Got it on 4.12.0-0.nightly-2022-07-25-055755.

Oh no! Something went wrong.

Cannot read properties of undefined (reading 'openshift.io/requester')

Component trace:
at B (https://console-openshift-console.apps.ci-ln-z9i3d8b-72292.origin-ci-int-gce.dev.rhcloud.com/static/main-chunk-af572409c47a3be7df6f.min.js:1:401818)
    at div
    at N (https://console-openshift-console.apps.ci-ln-z9i3d8b-72292.origin-ci-int-.....

Comment 3 Christoph Jerolimov 2022-08-31 09:03:47 UTC
As this was reported initially with nanokube, I've tested our latest console frontend with nanokube again. Could not find this crash anymore.

Tested with console master (commit b1669de492ba01919be737c23f5d7ce7e7fa4f05) and nanokube (commit fd5f3c5b5688665095f80cd0d0f24e6bcace57c7)

Comment 6 errata-xmlrpc 2023-01-17 19:53:34 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.12.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.