+++ This bug was initially created as a clone of Bug #1848244 +++ Created attachment 1697902 [details] pending pods error in UI Description of problem: While trying to investigate a cluster with Pending pods, by clicking on `Logs`, it bring up the `Oh no! Something went wrong` error. Version-Release number of selected component (if applicable): 4.5 How reproducible: When a pod is in pending state. Steps to Reproduce: 1. Get a pod in a pending state. The easiest way for me is to try to install metering with a cluster that has insufficent resource...worker nodes of only m1.large for example. Will cause the presto pod to be in the Pending state Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 4m11s (x30 over 31m) default-scheduler 0/7 nodes are available: 7 Insufficient cpu. 2. 3. Actual results: Error Description: Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. Error: Minified React error #185; visit https://reactjs.org/docs/error-decoder.html?invariant=185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at Tu (https://console-openshift-console.apps.wxj181-5422.qe.devcluster.openshift.com/static/vendors~main-chunk-19504135f53376dd474b.min.js:150:78405) at Object.enqueueSetState (https://console-openshift-console.apps.wxj181-5422.qe.devcluster.openshift.com/static/vendors~main-chunk-19504135f53376dd474b.min.js:150:46451) at t._.setState (https://console-openshift-console.apps.wxj181-5422.qe.devcluster.openshift.com/static/vendors~main-chunk-19504135f53376dd474b.min.js:142:1440) at https://console-openshift-console.apps.wxj181-5422.qe.devcluster.openshift.com/static/vendors~main-chunk-19504135f53376dd474b.min.js:12:98564 at r (https://console-openshift-console.apps.wxj181-5422.qe.devcluster.openshift.com/static/vendors~main-chunk-19504135f53376dd474b.min.js:19:27428) at https://console-openshift-console.apps.wxj181-5422.qe.devcluster.openshift.com/static/vendors~main-chunk-19504135f53376dd474b.min.js:19:27652 at Array.forEach (<anonymous>) at Object.notifyListeners (https://console-openshift-console.apps.wxj181-5422.qe.devcluster.openshift.com/static/vendors~main-chunk-19504135f53376dd474b.min.js:19:27623) at x (https://console-openshift-console.apps.wxj181-5422.qe.devcluster.openshift.com/static/vendors~main-chunk-19504135f53376dd474b.min.js:35:235687) at https://console-openshift-console.apps.wxj181-5422.qe.devcluster.openshift.com/static/vendors~main-chunk-19504135f53376dd474b.min.js:35:237265 Expected results: Additional info:
Waiting for 4.5.z to open.
PR opened, awaiting cherry pick approval.
Created attachment 1700944 [details] Verification screenshot
Checked on several Pendingpods, this is not reproduced. Verified on 4.5.0-0.nightly-2020-07-13-205047 (Attached the screenshot)
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, 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-2020:2909