Bug 1921603

Summary: Cannnot load deployment config in Openshift 4.6.9
Product: OpenShift Container Platform Reporter: Jaspreet Kaur <jkaur>
Component: Dev ConsoleAssignee: Christoph Jerolimov <cjerolim>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: urgent Docs Contact: Harsh Mishra <hmishra>
Priority: urgent    
Version: 4.6CC: aballant, aos-bugs, cjerolim, eparis, jokerman, juqiao, mzali, nmukherj, openshift-bugs-escalate, pmuller, rrahmat, spadgett, spathak, swasthan
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the application crashed when the correlated pod data was not available for the deployment config. This was because the console deployment fetched two sets of data with the pod status donut shown as soon as deployment config is loaded. If the API returns more than 250 pods, some of the information is skipped and is not available. This issue is fixed and the pod data is available even when the project contains more than 250 pods, thus ensuring that the *DeploymentConfig* detail page does not crash anymore.
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-22 13:54:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1922475    
Bug Blocks:    
Attachments:
Description Flags
Can load deployment config in Openshift 4.6.9
none
Cannnot load deployment config in Openshift 4.6 none

Description Jaspreet Kaur 2021-01-28 09:53:08 UTC
Description of problem: When a project has more than 700 deployment config it results in below error when opening the page.

(https://console-openshift-console.apps.example.com/k8s/ns/preprod-esb/deploymentconfigs/xyz-bs/)


```
vendors~main-chunk-097f186a6bd6062a5833.min.js:159202 TypeError: Cannot read property 'pods' of undefined
    at a.a (deployment-config~deployment-config-overview-chunk-c0930d19396ba7f0219b.min.js:1)
    at No (vendors~main-chunk-097f186a6bd6062a5833.min.js:159202)
    at Ks (vendors~main-chunk-097f186a6bd6062a5833.min.js:159202)
    at Bs (vendors~main-chunk-097f186a6bd6062a5833.min.js:159202)
    at Fs (vendors~main-chunk-097f186a6bd6062a5833.min.js:159202)
    at Ms (vendors~main-chunk-097f186a6bd6062a5833.min.js:159202)
    at vendors~main-chunk-097f186a6bd6062a5833.min.js:159202
    at t.unstable_runWithPriority (vendors~main-chunk-097f186a6bd6062a5833.min.js:159496)
    at li (vendors~main-chunk-097f186a6bd6062a5833.min.js:159202)
    at hi (vendors~main-chunk-097f186a6bd6062a5833.min.js:159202)
```




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


How reproducible:


Steps to Reproduce:
1. Create a project with 700+ dc 
2. Try to open the dc page it fails to load and gives js error
3.

Actual results: Unable to open the page for deployment configs

Expected results: should be able to open the page properly


Additional info:  project with less number of dc and pods doesnt give the same error. Only two projects which have more than 700 DC have this error.


we cannot open DC page directly (https://console-openshift-console.apps.example.com/k8s/ns/preprod-esb/deploymentconfigs/xyz-bs/) 

but able to open all of its tabs except for Details tab if we hit the url directly (https://console-openshift-console.apps.example.com/k8s/ns/preprod-esb/deploymentconfigs/xyz-bs/pod or https://console-openshift-console.apps.example.com/k8s/ns/preprod-esb/deploymentconfigs/xyz-bs/events)
so somehow error happens only on "Details tab"

Comment 3 Jakub Hadvig 2021-01-28 12:25:34 UTC
Im a bit confused from the screenshots attached. Is the error happening on the DC list page or the details page ?

Comment 10 Christoph Jerolimov 2021-01-29 20:50:03 UTC
I could reproduce this in 4.5 and 4.6. The frontend error happens if a DeploymentConfig detail page was open and the API call for get Pod list needs a second "page" call to get the right Pods. This happen if the active project (namespace) has more then 250 running Pods in it.

In 4.7 the code was already refactored and the new version doesn't contain this issue.

Comment 17 Christoph Jerolimov 2021-02-11 12:42:50 UTC
The issue is merged now and will be part of the next 4.6 release. I expect that will be 4.9.10.

Can we remove the needinfo attributes?

Comment 18 Christoph Jerolimov 2021-02-11 12:43:35 UTC
Oh it automatically disappear if I post something. Thanks BZ :)

Comment 19 spathak@redhat.com 2021-02-12 17:21:02 UTC
Created attachment 1756670 [details]
Can load deployment config in Openshift 4.6.9

Comment 20 spathak@redhat.com 2021-02-12 17:22:58 UTC
Created attachment 1756671 [details]
Cannnot load deployment config in Openshift 4.6

Comment 21 spathak@redhat.com 2021-02-12 17:25:05 UTC
Verified on build version: 4.6.17
Browser version: Chrome 84

Comment 24 errata-xmlrpc 2021-02-22 13:54:57 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.18 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-2021:0510

Comment 25 Red Hat Bugzilla 2023-09-15 00:59:27 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days