Total number of tests = 170 Final Result after filtering the tests from dont_run_tests.json, quarantined_tests.json and some more known issues:- 1] test_id:1616 : A new VirtualMachineInstance with IgnitionData annotation with injected data [test_id:1616]should have injected data under firmware directory 2] test_id:6967 : Configurations Block size configuration set [test_id:6967]Should set BlockIO when set to match volume block sizes on files 3] Configurations with automatic resource limits FG enabled when a ResourceQuota with memory limits is associated to the creation namespace should set a memory limit in the virt-launcher pod : Configurations with automatic resource limits FG enabled when a ResourceQuota with memory limits is associated to the creation namespace should set a memory limit in the virt-launcher pod 4] Configurations with automatic resource limits FG enabled when there is no ResourceQuota with memory limits associated with the creation namespace should not automatically set memory limits in the virt-launcher pod : Configurations with automatic resource limits FG enabled when there is no ResourceQuota with memory limits associated with the creation namespace should not automatically set memory limits in the virt-launcher pod 5] test_id:1643 : Creating a VirtualMachineInstance VirtualMachineInstance Emulation Mode [test_id:1643]should enable emulation in virt-launcher 6] test_id:1644 : Creating a VirtualMachineInstance VirtualMachineInstance Emulation Mode [test_id:1644]should be reflected in domain XML 7] test_id:1645 : Creating a VirtualMachineInstance VirtualMachineInstance Emulation Mode [test_id:1645]should request a TUN device but not KVM 8] test_id:4607 : GPU with ephemeral disk [test_id:4607]Should create a valid VMI but pod should not go to running state 9] test_id:4608 : GPU with ephemeral disk [test_id:4608]Should create a valid VMI and appropriate libvirt domain 10] Hyper-V enlightenments VMI with HyperV re-enlightenment enabled the vmi with EVMCS HyperV feature should have correct HyperV and cpu features auto filled EVMCS should be enabled when vmi.Spec.Domain.Features.Hyperv.EVMCS is set but the EVMCS.Enabled field is nil : Hyper-V enlightenments VMI with HyperV re-enlightenment enabled the vmi with EVMCS HyperV feature should have correct HyperV and cpu features auto filled EVMCS should be enabled when vmi.Spec.Domain.Features.Hyperv.EVMCS is set but the EVMCS.Enabled field is nil 11] Hyper-V enlightenments VMI with HyperV re-enlightenment enabled the vmi with EVMCS HyperV feature should have correct HyperV and cpu features auto filled hyperv and cpu features should be auto filled when EVMCS is enabled : Hyper-V enlightenments VMI with HyperV re-enlightenment enabled the vmi with EVMCS HyperV feature should have correct HyperV and cpu features auto filled hyperv and cpu features should be auto filled when EVMCS is enabled 12] KubeVirt control plane resilience pod eviction evicting pods of control plane eviction of multi-replica virt-api pod should succeed : KubeVirt control plane resilience pod eviction evicting pods of control plane eviction of multi-replica virt-api pod should succeed 13] KubeVirt control plane resilience pod eviction evicting pods of control plane eviction of single-replica virt-controller pod should succeed : KubeVirt control plane resilience pod eviction evicting pods of control plane eviction of single-replica virt-controller pod should succeed 14] NonRoot feature [verify-nonroot] NonRoot feature Fails if can't be tested : NonRoot feature [verify-nonroot] NonRoot feature Fails if can't be tested 15] test_id:4136 : Prometheus Endpoints [test_id:4136][flaky] should find one leading virt-controller and two ready 16] test_id:6243 : Prometheus Endpoints should include VMI eviction blocker status for all running VMs [test_id:6243] by IPv6 17] test_id:6241 : Prometheus Endpoints should include VMI infos for a running VM [test_id:6241] by IPv6 18] test_id:6242 : Prometheus Endpoints should include VMI phase metrics for all running VMs [test_id:6242] by IPv6 19] test_id:6244 : Prometheus Endpoints should include kubernetes labels to VMI metrics [test_id:6244] by IPv6 20] test_id:6236 : Prometheus Endpoints should include metrics for a running VM [test_id:6236] network metrics by IPv6 21] test_id:6237 : Prometheus Endpoints should include metrics for a running VM [test_id:6237] memory metrics by IPv6 22] test_id:6238 : Prometheus Endpoints should include metrics for a running VM [test_id:6238] vcpu wait by IPv6 23] test_id:6239 : Prometheus Endpoints should include metrics for a running VM [test_id:6239] vcpu seconds by IPv6 24] test_id:6240 : Prometheus Endpoints should include metrics for a running VM [test_id:6240] vmi unused memory by IPv6 25] test_id:6245 : Prometheus Endpoints should include swap metrics [test_id:6245] by IPv6 26] test_id:6227 : Prometheus Endpoints should include the metrics for a running VM [test_id:6227] by using IPv6 27] test_id:6228 : Prometheus Endpoints should include the storage metrics for a running VM [test_id:6228] storage flush requests metric by using IPv6 28] test_id:6229 : Prometheus Endpoints should include the storage metrics for a running VM [test_id:6229] time (ms) spent on cache flushing metric by using IPv6 29] test_id:6230 : Prometheus Endpoints should include the storage metrics for a running VM [test_id:6230] I/O read operations metric by using IPv6 30] test_id:6231 : Prometheus Endpoints should include the storage metrics for a running VM [test_id:6231] I/O write operations metric by using IPv6 31] test_id:6232 : Prometheus Endpoints should include the storage metrics for a running VM [test_id:6232] storage read operation time metric by using IPv6 32] test_id:6233 : Prometheus Endpoints should include the storage metrics for a running VM [test_id:6233] storage read traffic in bytes metric by using IPv6 33] test_id:6234 : Prometheus Endpoints should include the storage metrics for a running VM [test_id:6234] storage write operation time metric by using IPv6 34] test_id:6235 : Prometheus Endpoints should include the storage metrics for a running VM [test_id:6235] storage write traffic in bytes metric by using IPv6 35] test_id:6226 : Prometheus Endpoints should throttle the Prometheus metrics access [test_id:6226] by using IPv6 36] test_id:5843 : Syspreped VirtualMachineInstance [ref_id:5105]should create the Admin user as specified in the Autounattend.xml [test_id:5843]Should run echo command on machine using the credentials specified in the Autounattend.xml file 37] test_id:5004 : VM Live Migration Starting a VirtualMachineInstance [Serial] migration postcopy with datavolume [test_id:5004] should be migrated successfully, using guest agent on VM with postcopy 38] test_id:8610 : VM Live Migration Starting a VirtualMachineInstance [Serial] migration to nonroot should migrate root implementation to nonroot [test_id:8610] with DataVolume 39] test_id:8612 : VM Live Migration Starting a VirtualMachineInstance [Serial] migration to nonroot should migrate root implementation to nonroot [test_id:8612] with PVC 40] VM Live Migration Starting a VirtualMachineInstance [Serial] migration to root should migrate nonroot implementation to root with DataVolume : VM Live Migration Starting a VirtualMachineInstance [Serial] migration to root should migrate nonroot implementation to root with DataVolume 41] VM Live Migration Starting a VirtualMachineInstance [Serial] migration to root should migrate nonroot implementation to root with PVC : VM Live Migration Starting a VirtualMachineInstance [Serial] migration to root should migrate nonroot implementation to root with PVC 42] test_id:2653 : VM Live Migration Starting a VirtualMachineInstance with a Fedora shared NFS PVC (using nfs ipv4 address), cloud init and service account [test_id:2653] should be migrated successfully, using guest agent on VM with default migration configuration 43] test_id:6975 : VM Live Migration Starting a VirtualMachineInstance with a Fedora shared NFS PVC (using nfs ipv4 address), cloud init and service account [test_id:6975] should have guest agent functional after migration 44] test_id:6984 : VM Live Migration [Serial] With Huge Pages should consume hugepages [test_id:6984]hugepages-1Gi 45] VM Live Migration [Serial] with CPU pinning and huge pages and NUMA passthrough should not make migrations fail : VM Live Migration [Serial] with CPU pinning and huge pages and NUMA passthrough should not make migrations fail 46] test_id:3245 : VM Live Migration with a live-migrate eviction strategy set [Serial] VM Live Migration with a live-migrate eviction strategy set [Serialwith multiple VMIs with eviction policies set [release-blocker][test_id:3245]should not migrate more than two VMIs at the same time from a node 47] test_id:2666 : VMI definition [Serial]with sidecar feature gate disabled [test_id:2666]should not start with hook sidecar annotation 48] test_id:3155 : VMI definition set sidecar resources [test_id:3155][serial]should successfully start with hook sidecar annotation 49] test_id:3156 : VMI definition with SM BIOS hook sidecar [test_id:3156]should successfully start with hook sidecar annotation for v1alpha2 50] test_id:3157 : VMI definition with SM BIOS hook sidecar [test_id:3157]should call Collect and OnDefineDomain on the hook sidecar 51] test_id:3158 : VMI definition with SM BIOS hook sidecar [test_id:3158]should update domain XML with SM BIOS properties 52] VMI definition with SM BIOS hook sidecar should not start with hook sidecar annotation when the version is not provided : VMI definition with SM BIOS hook sidecar should not start with hook sidecar annotation when the version is not provided 53] test_id:1684 : VirtualMachineInstance with CPU pinning [Serial]with cpu pinning enabled [test_id:1684]should set the cpumanager label to false when it's not running 54] test_id:4632 : VirtualMachineInstance with CPU pinning [Serial]with cpu pinning enabled [test_id:4632]should be able to start a vm with guest memory different from requested and keep guaranteed qos 55] Windows VirtualMachineInstance with winrm connection VMI with subdomain is created should have the domain set properly with subdomain : Windows VirtualMachineInstance with winrm connection VMI with subdomain is created should have the domain set properly with subdomain 56] test_id:240 : Windows VirtualMachineInstance with winrm connection [ref_id:139]VMI is created [test_id:240]should have correct UUID 57] test_id:3159 : Windows VirtualMachineInstance with winrm connection [ref_id:139]VMI is created [test_id:3159]should have default masquerade IP 58] test_id:3160 : Windows VirtualMachineInstance with winrm connection [ref_id:139]VMI is created [test_id:3160]should have the domain set properly 59] Windows VirtualMachineInstance with winrm connection with bridge binding should be recognized by other pods in cluster : Windows VirtualMachineInstance with winrm connection with bridge binding should be recognized by other pods in cluster 60] test_id:3154 : With ServiceMonitor Disabled [test_id:3154]Should not create RBAC Role or RoleBinding for ServiceMonitor 61] test_id:4615 : [Serial][sig-operator]Operator With PrometheusRule Disabled [test_id:4615]Checks that we do not deploy a PrometheusRule cr when not needed 62] test_id:4614 : [Serial][sig-operator][sig-operatorOperator With PrometheusRule Enabled [test_id:4614]Checks if the kubevirt PrometheusRule cr exists and verify it's spec 63] test_id:4105 : [level:componentcertificates should be rotated when deleted for [test_id:4105] virt-handlers client side 64] test_id:3149 : infrastructure management [test_id:3149]should be able to create kubevirt install with image prefix 65] test_id:4613 : infrastructure management [test_id:4613]should remove owner references on non-namespaces resources when updating a resource 66] vitiofs config volumes With a DownwardAPI defined Should be the namespace and token the same for a pod and vmi with virtiofs : vitiofs config volumes With a DownwardAPI defined Should be the namespace and token the same for a pod and vmi with virtiofs 67] vitiofs config volumes With a ServiceAccount defined Should be the namespace and token the same for a pod and vmi with virtiofs : vitiofs config volumes With a ServiceAccount defined Should be the namespace and token the same for a pod and vmi with virtiofs 68] vitiofs config volumes With a single ConfigMap volume Should be the mounted virtiofs layout the same for a pod and vmi : vitiofs config volumes With a single ConfigMap volume Should be the mounted virtiofs layout the same for a pod and vmi 69] vitiofs config volumes With a single Secret volume Should be the mounted virtiofs layout the same for a pod and vmi : vitiofs config volumes With a single Secret volume Should be the mounted virtiofs layout the same for a pod and vmi 70] test_id:3292 : with RHEL Template [test_id:3292]should succeed to create VirtualMachine via oc command 71] test_id:3293 : with RHEL Template [test_id:3293]should fail to delete VirtualMachine via oc command 72] test_id:3294 : with RHEL Template when the VirtualMachine was created [test_id:3294]should succeed to start the VirtualMachine via oc command 73] test_id:3295 : with RHEL Template when the VirtualMachine was created [test_id:3295]should succeed to delete VirtualMachine via oc command 74] test_id:3308 : with RHEL Template when the VirtualMachine was created [test_id:3308]should fail to create the same VirtualMachine via oc command 75] test_id:8607 : with TPM VMI option enabled [test_id:8607] should expose a functional emulated TPM which persists across migrations 76] with hugepages should consume hugepages [Serial]hugepages-2Mi with passt enabled : with hugepages should consume hugepages [Serial]hugepages-2Mi with passt enabled