Bug 1828829
| Summary: | Filter in VM/VMT list view remains active after found resource is deleted | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Radim Hrazdil <rhrazdil> | ||||
| Component: | Console Kubevirt Plugin | Assignee: | Yaacov Zamir <yzamir> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Radim Hrazdil <rhrazdil> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.5 | CC: | aos-bugs, yzamir | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-07-13 17:32:20 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: |
|
||||||
Verified in console release-4.5 branch commit: 5994c64ee529b650bae348ef78ebc23dca8db5c5 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:2409 |
Created attachment 1682458 [details] video sample Description of problem: When a user deletes a resource (VM/VMI/VMT) in UI list view with an active filter, this filter remains active afther the resource has been deleted. Later if new VM is created using CLI (or in another browser tab), the VM is not displayed because of the active fiter We should re-populate the filter when a new resource exists, that is not visible due to active filter - at least this is how it works in core OCP. Version-Release number of selected component (if applicable): 4.5 How reproducible: 100% Steps to Reproduce: 1. Create a VM, navigate to Virtualization -> Virtual Machines 2. Filter for name of the created VM 3. Delete it using the kebab menu 4. Use CLI to create another VM in the same namespace Actual results: The new VM is not displayed in the UI because the filter is still active, despite not being visible Expected results: Additional info: