Bug 2100436
| Summary: | VM list filtering ignores VMs in error-states | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Leon Kladnitsky <lkladnit> | ||||
| Component: | User Experience | Assignee: | Ugo Palatucci <upalatuc> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Leon Kladnitsky <lkladnit> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.11.0 | CC: | upalatuc, ycui | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.12.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: | 2023-01-24 13:36:39 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 on v.4.12.109-6 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 (Important: OpenShift Virtualization 4.12.0 Images security update), 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/RHSA-2023:0408 |
Created attachment 1892117 [details] filtering Description of problem: VM list view has a filter which does not relate to VMs in erroneous states. These VMs are listed for all filtering options. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a VM from any RHEL template, leave Disk source as default, click "Review and create VirtualMachine", then "Create VirtualMachine" 2. Ignore "No available boot source" warning and create the VM. 3. Clone the VM and start the cloned VM. It will have "ErrorDataVolumeNotFound" status. Actual results: 4. Click Filter dropdown and look at the figures (broken VMs are ignored) 5. Check filtering for "Running", "Paused", "Stopped" etc. (broken VMs are always listed) 6. Click kebab menu of broken VM (Stop and Restart options are enabled) Expected results: 4. Filter menu should have option to filter broken VMs. 5. Broken VMs should be listed only with their own filter, not in Running/Paused etc. 6. Broken VM should not have Stop and Restart as available command. Additional info: If broken VM is stopped it is listed as stopped VM, without error tags.