Bug 1848244 - clicking on Logs to view details on Pending pods cause the dreaded `Oh no! Something went wrong` error to display
Summary: clicking on Logs to view details on Pending pods cause the dreaded `Oh no! So...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.6.0
Assignee: Yadan Pei
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks: 1849213
TreeView+ depends on / blocked
 
Reported: 2020-06-18 04:36 UTC by Peter Ruan
Modified: 2020-10-27 16:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:08:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
pending pods error in UI (481.53 KB, image/png)
2020-06-18 04:36 UTC, Peter Ruan
no flags Details
Pending Pod Logs tab works (133.38 KB, image/png)
2020-06-29 07:54 UTC, Yadan Pei
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5780 0 None closed Bug 1848244: Fix bug where pending pod log tab throws error 2020-07-14 03:22:00 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:08:39 UTC

Description Peter Ruan 2020-06-18 04:36:57 UTC
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:

Comment 1 Robb Hamilton 2020-06-19 20:39:00 UTC
PR merged, waiting on QE verification.

Comment 2 Peter Ruan 2020-06-20 15:15:13 UTC
still has not hit 4.5 nightly yet.  But it's in payload: https://openshift-release.svc.ci.openshift.org//releasestream/4.6.0-0.ci/release/4.6.0-0.ci-2020-06-19-220643

Comment 5 Yadan Pei 2020-06-29 07:54:32 UTC
Created attachment 1699090 [details]
Pending Pod Logs tab works

1. Create several pods to use up resource, then new pods will become Pending
2. View Logs tab for Pending pod, this time no runtime error

Verified on 4.6.0-0.nightly-2020-06-26-035408

Comment 7 errata-xmlrpc 2020-10-27 16:08:03 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.6 GA Images), 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:4196


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