Bug 1808611

Summary: Filter Helm Release Resources by name gives an error
Product: OpenShift Container Platform Reporter: cvogt
Component: Dev ConsoleAssignee: Jeff Phillips <jephilli>
Status: CLOSED ERRATA QA Contact: Ruchir Garg <rgarg>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, jephilli, nmukherj, rgarg, sbudhwar
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1808489 Environment:
Version: 4.5.0-0.ci-2020-02-28-072816 Cluster ID: d2143643-a7aa-4b6a-9120-10dabf90d47b Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.122 Safari/537.36
Last Closed: 2020-05-04 11:43:49 UTC Type: ---
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: 1808489    
Bug Blocks:    

Description cvogt 2020-02-29 00:47:52 UTC 
+++ This bug was initially created as a clone of Bug #1808489 +++

Description of problem:

In the Helm Release Resources page, most of the List actions like sorting any of the fields, changing filtertext breaks the flow and throws the user a white error page.

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


How reproducible:

always

Steps to Reproduce:
1. In the Developer perspective, go to `More` -> `Helm`
2. click on a helm release
3. In the Details page, click on the Resources tab
4. type something in the filter text box or sort any of the fields.

Actual results:

the page fails to load & errors are logged in the browser's console

Expected results:

it should filter the resources by the keyword entered in the filter text box and sort the columns without any error.

Additional info:
Comment 4 errata-xmlrpc 2020-05-04 11:43:49 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, 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:0581