Bug 2017130

Summary: t is not a function error navigating to details page
Product: OpenShift Container Platform Reporter: cvogt
Component: Dev ConsoleAssignee: cvogt
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: medium Docs Contact:
Priority: urgent    
Version: 4.8CC: alkazako, aos-bugs, bmozaffa, jduimovich, kjeeyar, nmukherj, spathak, yzha
Target Milestone: ---Flags: cvogt: needinfo-
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
* Before this update, if you repeatedly clicked links to get details for resources such as custom resource definitions or pods and the application encountered multiple code reference errors, it crashed and displayed a `t is not a function` error. This update resolves the issue. When an error occurs, the application resolves a code reference and stores the resolution state so that it can correctly handle additional errors. The application no longer crashes when code reference errors occur. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2017130[BZ#2017130])
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:21:40 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:    
Bug Blocks: 2022158    
Attachments:
Description Flags
page error
none
console error none

Description cvogt 2021-10-25 17:48:10 UTC
Description of problem:
Randomly a error can occur rendering the details page inaccessible to the user and instead they are presented with a page error.


Version-Release number of selected component (if applicable):
4.8.13 dbaas test instance
4.8.15 dev sandbox

note: both installations have the telemetry plugin installed


How reproducible:


Steps to Reproduce:
1. open the admin perspective
2. visit a list page (eg custom resource definition, pods, etc...)
3. visit details pages of one of the resources
4. keep repeating step 2 and 3 until error occurs

Actual results:
`t is not a function` error (see attached screenshots


Expected results:
No error should occur


Additional info:
- telemetry plugin installed may or may not have an affect
- error is random
- refreshing the page will often clear the error

Comment 1 cvogt 2021-10-25 17:49:01 UTC
Created attachment 1836944 [details]
page error

Comment 2 cvogt 2021-10-25 17:49:32 UTC
Created attachment 1836945 [details]
console error

Comment 3 John Duimovich 2021-10-26 15:42:37 UTC
 
A few more data points.

If you logout and re-login --- the Project pages displays properly, but if you click off and re - click on project the error returns. 
If you refresh the page with a hard - shift refresh, the page shows, but if you click off and select again the page you get an error. 
Both are repeatable.

Video reproduction here (rh visible) https://drive.google.com/file/d/1XXJKQvJ3omekGalWZ2yYTxsoSV4xIxJ4/view?usp=sharing

Comment 5 cvogt 2021-11-03 13:51:47 UTC
With devsandbox updated to 4.9, I can no longer reproduce this issue following the steps in John's video above.

Comment 6 Yu Zhao 2021-11-03 17:21:56 UTC
Please kindly note that this issue does not exist on 4.9 clusters. However, it DOES exist on 4.8 clusters, which has serious impact on our users. We would be highly appreciated, if this issue can be fixed ASAP.

Comment 10 spathak@redhat.com 2021-11-16 12:46:37 UTC
Tried the following scenarios given in the bug
> visit list pages of custom resource definition, pods, deployments, etc.
> visit details pages of one of the resources
> logout and re-login, go to Project pages in developer perspective then click off and re-click on the project tab
> refresh the page with a hard-shift refresh, go to Project pages in developer perspective, then click off and select again the project tab 

Couldn't generate the error, tried on build version 4.10.0-0.nightly-2021-11-14-184249 and browser version Chrome 90

Comment 11 Yu Zhao 2021-11-16 15:34:44 UTC
@spathak Can we check if the issue is fixed on 4.8 clusters? As far as I know, this issue only exist on 4.8 clusters, and it does not exist on 4.9 or 4.10 clusters. Thanks!

Comment 13 Yu Zhao 2021-11-18 14:54:35 UTC
@spathak As far as I checked, this issue exist on OCP 4.8 clusters, and it does not exist on OCP 4.9 clusters or OCP 4.10 clusters. So, can we test it on a OCP 4.8 cluster? Thanks

Comment 17 errata-xmlrpc 2022-03-10 16:21:40 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.10.3 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.

https://access.redhat.com/errata/RHSA-2022:0056

Comment 18 Red Hat Bugzilla 2023-09-15 01:36:46 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days