Description of problem: We've notice on our CI that during testing a blank white page appeared, and ODC don't load anything after 60s of wait time. We've noticed it appearing on: * Topology List view - /topology/ns/serverless-tests/list * Deploy Image - /deploy-image/ns/serverless-tests * +Add - /add/ns/serverless-tests Version-Release number of selected component (if applicable): quay.io/openshift-release-dev/ocp-release@sha256:5fb4b4225498912357294785b96cde6b185eaed20bbf7a4d008c462134a4edfd How reproducible: Flaky Steps to Reproduce: 1. Trying to open one of those listed pages?! Hard to tell. Actual results: A white blank page is displayed and ODC do not load anything after a long while (60sec) Expected results: Page content should appear. At least the ODC headers, or error message should appear. Additional info: This behavior can be seen on Cypress testing video: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832/artifacts/e2e-aws-ocp-48-continuous/serverless-e2e/artifacts/build-6Z+HU1sA/ui/videos/serving.spec.js.mp4 Also, it's visible on screenshots: 1. topology list view 1.1. https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832/artifacts/e2e-aws-ocp-48-continuous/serverless-e2e/artifacts/build-6Z+HU1sA/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20deploy%20a%20cluster-local%20service%20--%20after%20each%20hook%20(failed).png 1.2. https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832/artifacts/e2e-aws-ocp-48-continuous/serverless-e2e/artifacts/build-6Z+HU1sA/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20route%20traffic%20to%20multiple%20revisions%20(failed).png 1.3. https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832/artifacts/e2e-aws-ocp-48-continuous/serverless-e2e/artifacts/build-6Z+HU1sA/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20route%20traffic%20to%20multiple%20revisions%20(failed)%20(attempt%202).png 2. +add 2.1. https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832/artifacts/e2e-aws-ocp-48-continuous/serverless-e2e/artifacts/build-6Z+HU1sA/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20deploy%20a%20cluster-local%20service%20(failed)%20(attempt%202).png 2.2. https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832/artifacts/e2e-aws-ocp-48-continuous/serverless-e2e/artifacts/build-6Z+HU1sA/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20route%20traffic%20to%20multiple%20revisions%20(failed)%20(attempt%203)%20(1).png 3. deploy image 3.1. https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832/artifacts/e2e-aws-ocp-48-continuous/serverless-e2e/artifacts/build-6Z+HU1sA/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20deploy%20a%20cluster-local%20service%20(failed)%20(attempt%203).png 3.2. https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832/artifacts/e2e-aws-ocp-48-continuous/serverless-e2e/artifacts/build-6Z+HU1sA/ui/screenshots/serving.spec.js/OCP%20UI%20for%20Serverless%20--%20can%20route%20traffic%20to%20multiple%20revisions%20(failed)%20(attempt%203).png That's 7 errors in a single CI run. CI run: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832
We are using cluster-pools on the CI so that actual version of OCP was 4.8.3 in this case. As can be seen here: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435392732074872832/artifacts/e2e-aws-ocp-48-continuous/gather-extra/artifacts/clusterversion.json
Another fun affected by this issue. This time cluster was in 4.8.10 version. https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-knative-serverless-operator-main-4.8-e2e-aws-ocp-48-continuous/1435754908740489216
Created attachment 1823414 [details] UI test logs with cypress-terminal-report plugion to try to display ODC logs A log on reproduction on OCP 4.8.10. This is running with this commit https://github.com/cardil/serverless-operator/commit/e6d8bf0e6e8cc372b5c57399c4cb41f95aa3a280 that adds a cypress-terminal-report plugin so that ODC logs could be visible in case of failure.
Created attachment 1823416 [details] Visible blank white screen after 60 seconds from previous command
Comment on attachment 1823414 [details] UI test logs with cypress-terminal-report plugion to try to display ODC logs The error - blank screen happens at line 1149 in the log. And the command that surely succeed is at line 1071. So maybe some massage between lines 1071-1149 could lead to this blank screen. Maybe, it might be some non handled exception?!?
After discussion with @jakumar we think the root cause probably lay in ODC code base. The exception could be seen at lines 1162-1171 of attached log. That leads to ODC code, although in minified compiled form. ``` cons:error ✘ TypeError: Cannot read property 'kind' of null at I (https://console-openshift-console.apps.ksuszyns-308-ocp4x-aws-clean.openshift-aws.rhocf-dev.net/static/dev-console-edit-chunk-ade0d1bba0a484b9cd 28.min.js:1:108158) at $ (https://console-openshift-console.apps.ksuszyns-308-ocp4x-aws-clean.openshift-aws.rhocf-dev.net/static/dev-console-edit-chunk-ade0d1bba0a484b9cd 28.min.js:1:110175) at https://console-openshift-console.apps.ksuszyns-308-ocp4x-aws-clean.openshift-aws.rhocf-dev.net/static/dev-console-edit-chunk-ade0d1bba0a484b9cd28. min.js:1:116126 at K (https://console-openshift-console.apps.ksuszyns-308-ocp4x-aws-clean.openshift-aws.rhocf-dev.net/static/dev-console-edit-chunk-ade0d1bba0a484b9cd 28.min.js:1:116295) at t.a (https://console-openshift-console.apps.ksuszyns-3 ... ```
I have verified on 4.9.23 that https://github.com/openshift/console/pull/9253 solves that the console doesn't crash anymore when edit a Deployment, a DeploymentConfig and a Serverless Service that doesn't exist. Chris (@ksuszyns) would you like to review/verify this PR here as well or #2060616 (after it is closed and available for 4.8 as well)?
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.24 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. https://access.redhat.com/errata/RHBA-2022:0798