Created attachment 1885800 [details] "VMCannotBeEvicted" alert raised Description of problem: Currently when running on SNO, for VMs that are created using common templates, Alerts of "Warning Severity" with the name "VMCannotBeEvicted" will be raised. Version-Release number of selected component (if applicable): 4.11 How reproducible: 100% Steps to Reproduce: 1. On an SNO cluster 2. Create a VM from a common template with eviction strategy Actual results: An Alert "VMCannotBeEvicted" is raised Expected results: An Alert "VMCannotBeEvicted" should not be raised Additional info: This is a known issue, it will be fixed when "Cluster level eviction strategy" will be implemented, and we will remove the eviction strategy from the templates.
This issue is not resolved, please include the known issue in the 4.12 GA release notes, thanks!
@aspauldi please add the known issue to the 4.12 release notes
retarget to 4.14 to stay in sync with https://issues.redhat.com/browse/CNV-13720
@sgott I think that https://github.com/kubevirt/hyperconverged-cluster-operator/pull/2376 + https://gitlab.cee.redhat.com/cpaas-midstream/openshift-virtualization/kubevirt-ssp-operator/-/merge_requests/473 should cover all the cases for the target release. Thanks
In that case can this BZ be moved to POST?
Do not include as a known issue in the 4.14 release notes - issue is fixed for 4.14. Please work with the SME to add a description of the fix so that we can show that the known issue is now resolved. Thanks
Removed from CNV 4.14 Release Notes Known issues section and added to Bug fix section. Jira: https://issues.redhat.com//browse/CNV-20106 PR: https://github.com/openshift/openshift-docs/pull/66054
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.14.0 Images security and bug fix 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:6817