Bug 1857399
| Summary: | Events page leftover resource chip after clearing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Gina Doyle <gdoyle> | ||||
| Component: | Management Console | Assignee: | Zac Herman <zherman> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.6 | CC: | aos-bugs, jhadvig, jokerman, yapei | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.6.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: | 2020-10-27 16:14:43 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: | |||||||
| Attachments: |
|
||||||
Moving to next sprint as this has not been QA'ed. Removing "All" chip is just like removing any other filter chip, will show all resources. Also "All Resources" is entirely removed from the dropdown. Checked the discuss in PR and this is the expected. So this issue could be Verified on 4.6.0-0.nightly-2020-09-09-224210 The only thing is the "All" chip is automatically added for initial filter. Is it a little confused? (In reply to XiaochuanWang from comment #4) > > The only thing is the "All" chip is automatically added for initial filter. > Is it a little confused? We did discuss the "All" chip on initial load and decided we would leave it that way for now so it was clear we were showing all to users when they first got to page. Thanks Zan, then this issue could be Verified on 4.6.0-0.nightly-2020-09-09-224210 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 (OpenShift Container Platform 4.6 GA Images), 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:4196 |
Created attachment 1701294 [details] Screenshots of the flow of how to get the bug Description of problem: On the Events page, after clearing a single resource chip (the "x" related to a single resource rather than the "x" of the resource chip group), a "resource" chip is left stranded after closing and there is no way of getting rid of it. Version-Release number of selected component (if applicable): 4.6 How reproducible: Always Steps to Reproduce: 1. Go to events page 2. Add a resource (ex. APIServer) 3. Click on the "x" within the white resource chip 4. You should see a gray chip that says "Resource" that does not allow you to interact with it Actual results: Gray chip that says "Resource" that does not allow you to interact with it Expected results: "Resource" chip group with the "All" white chip within the group. This should be the same result you would get by clicking the "x" on the gray chip group (rather than the individual chip). Additional info: