Description of problem: Cluser admin goes to ClusterSerivceClass page -> Service Plans tab page, filter Cluster Service Plans by name, when cursor clicked into input box and input something, the web page is frozen. Version-Release number of selected component (if applicable): 4.1.0-0.nightly-2019-08-30-035445 How reproducible: Always Steps to Reproduce: 1. Cluster admin user goes to Catalog -> Broker Management -> Service Classes tab page -> choose a servcieclass 2. Choose a serviceclass -> goes to Service Plans tab page 3. Find the filter box "Filter Cluster Service Plans by name", input something Actual results: Browser is frozen, have to wait. Expected results: Browser should work normally Additional info:
This is also seen on following page: Catalog -> Installed Operators -> choose one operator such as "Cluster Logging" -> click "Cluster Logging" tab page -> input in filter box
(In reply to XiaochuanWang from comment #1) > This is also seen on following page: > Catalog -> Installed Operators -> choose one operator such as "Cluster > Logging" -> click "Cluster Logging" tab page -> input in filter box This second problem is a duplicate of bug 1722876 and previously fixed by https://github.com/openshift/console/pull/1863
The bug fix: https://github.com/openshift/console/pull/2575 Will verify it on latest payload image.
Original steps are not reproducible. Comment 1 is still reproduced, input something will freeze the browser for a few seconds. Either reopen https://bugzilla.redhat.com/show_bug.cgi?id=1722876 or keep this one. Tested on 4.1.0-0.nightly-2019-09-09-223953
> Tested on 4.1.0-0.nightly-2019-09-09-223953 Fix version is 4.2, not 4.1
Now both the original and comment 1 are not reproduced on 4.2.0-0.nightly-2019-09-11-202233. It should be Verified.
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-2019:2922