Bug 1840256

Summary: Deselecting and selecting Application grouping throws exception on Firefox
Product: OpenShift Container Platform Reporter: Jeff Phillips <jephilli>
Component: Dev ConsoleAssignee: Jeff Phillips <jephilli>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Version: 4.5.0-0.ci-2020-05-26-081827 Cluster ID: 2b906c42-8514-4828-a46d-f7b0e14136b8 Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36
Last Closed: 2020-07-13 17:41:38 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:

Description Jeff Phillips 2020-05-26 16:14:06 UTC
Description of problem:

Deselecting and selecting Application grouping throws exception and page ends up with white screen.

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

How reproducible:

Only on Firefox

Steps to Reproduce:
1. Launch Developer console on Firefox browser
2. Switch to Developer perspective
3. Navigate to topology page & select a project which has Event source
4. Deselect & select `Event Sources` from Display options dropdown

Actual results:

Deselecting and selecting Event sources throws exception and page ends up with white screen.

Expected results:

On deselecting Event sources, all Event sources should hide & on Selecting Event sources, all Event sources should display.

Additional info:

Comment 3 spathak@redhat.com 2020-06-01 22:23:07 UTC
Verified on build version: 4.5.0-0.ci-2020-05-29-203954
Browser version: Firefox 73

Comment 4 errata-xmlrpc 2020-07-13 17:41:38 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.