Bug 1747918
| Summary: | Service plans tab page filter for CluserSerivceClass page will drag down web console | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | XiaochuanWang <xiaocwan> |
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.z | CC: | aos-bugs, jokerman |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:39:32 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: | |||
|
Description
XiaochuanWang
2019-09-02 09:06:57 UTC
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 |