Total number of tests = 177 Final Result after filtering the tests from dont_run_tests.json, quarantined_tests.json and some more known issues:- 1] A VirtualMachineInstance with usbredir support with an usbredir connection Should work in parallel : A VirtualMachineInstance with usbredir support with an usbredir connection Should work in parallel 2] A VirtualMachineInstance with usbredir support with an usbredir connection Should work several times : A VirtualMachineInstance with usbredir support with an usbredir connection Should work several times 3] A VirtualMachineInstance without usbredir support should fail to connect to VMI's usbredir socket : A VirtualMachineInstance without usbredir support should fail to connect to VMI's usbredir socket 4] test_id:1616 : A new VirtualMachineInstance with IgnitionData annotation with injected data [test_id:1616]should have injected data under firmware directory 5] 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 6] 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 7] test_id:1630 : Creating a VirtualMachineInstance with user-data without k8s secret [test_id:1630]should log warning and proceed once the secret is there 8] 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 9] 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 10] test_id:4136 : Prometheus Endpoints [test_id:4136][flaky] should find one leading virt-controller and two ready 11] test_id:6243 : Prometheus Endpoints should include VMI eviction blocker status for all running VMs [test_id:6243] by IPv6 12] test_id:6241 : Prometheus Endpoints should include VMI infos for a running VM [test_id:6241] by IPv6 13] test_id:6242 : Prometheus Endpoints should include VMI phase metrics for all running VMs [test_id:6242] by IPv6 14] test_id:6244 : Prometheus Endpoints should include kubernetes labels to VMI metrics [test_id:6244] by IPv6 15] test_id:6236 : Prometheus Endpoints should include metrics for a running VM [test_id:6236] network metrics by IPv6 16] test_id:6237 : Prometheus Endpoints should include metrics for a running VM [test_id:6237] memory metrics by IPv6 17] test_id:6238 : Prometheus Endpoints should include metrics for a running VM [test_id:6238] vcpu wait by IPv6 18] test_id:6239 : Prometheus Endpoints should include metrics for a running VM [test_id:6239] vcpu seconds by IPv6 19] test_id:6240 : Prometheus Endpoints should include metrics for a running VM [test_id:6240] vmi unused memory by IPv6 20] test_id:6245 : Prometheus Endpoints should include swap metrics [test_id:6245] by IPv6 21] test_id:6227 : Prometheus Endpoints should include the metrics for a running VM [test_id:6227] by using IPv6 22] test_id:6228 : Prometheus Endpoints should include the storage metrics for a running VM [test_id:6228] storage flush requests metric by using IPv6 23] 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 24] 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 25] 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 26] 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 27] 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 28] 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 29] 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 30] test_id:6226 : Prometheus Endpoints should throttle the Prometheus metrics access [test_id:6226] by using IPv6 31] test_id:1467 : Starting with virtio-win with virtio-win as secondary disk [test_id:1467]Starting with virtio-win with virtio-win as secondary disk [test_id:1467should boot and have the virtio as sata CDROM 32] 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 33] 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 34] 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 35] 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 36] test_id:6984 : VM Live Migration [Serial] With Huge Pages should consume hugepages [test_id:6984]hugepages-1Gi 37] test_id:2666 : VMI definition [Serial]with sidecar feature gate disabled [test_id:2666]should not start with hook sidecar annotation 38] test_id:3155 : VMI definition set sidecar resources [test_id:3155][serial]should successfully start with hook sidecar annotation 39] test_id:3156 : VMI definition with SM BIOS hook sidecar [test_id:3156]should successfully start with hook sidecar annotation for v1alpha2 40] test_id:3157 : VMI definition with SM BIOS hook sidecar [test_id:3157]should call Collect and OnDefineDomain on the hook sidecar 41] test_id:3158 : VMI definition with SM BIOS hook sidecar [test_id:3158]should update domain XML with SM BIOS properties 42] 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 43] 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 44] 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 45] 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 46] test_id:240 : Windows VirtualMachineInstance with winrm connection [ref_id:139]VMI is created [test_id:240]should have correct UUID 47] test_id:3159 : Windows VirtualMachineInstance with winrm connection [ref_id:139]VMI is created [test_id:3159]should have default masquerade IP 48] test_id:3160 : Windows VirtualMachineInstance with winrm connection [ref_id:139]VMI is created [test_id:3160]should have the domain set properly 49] 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 50] test_id:4134 : [level:componentTaints and toleration CriticalAddonsOnly taint set on a node [test_id:4134] kubevirt components on that node should not evict 51] [level:component[sig-compute]VirtualMachine A valid VirtualMachine given cpu/memory in requests/limits should allow int type : [level:component[sig-compute]VirtualMachine A valid VirtualMachine given cpu/memory in requests/limits should allow int type 52] [sig-compute] Instancetype and Preferences VirtualMachine using preference resource requirements should be accepted when VirtualMachine meets CPU (preferSockets default) requirements : [sig-compute] Instancetype and Preferences VirtualMachine using preference resource requirements should be accepted when VirtualMachine meets CPU (preferSockets default) requirements 53] test_id:7672 : [sig-compute]Pausing A valid VMI when unpaused via virtctl with --dry-run flag [test_id:7672]Pausing A valid VMI when unpaused via virtctl with --dry-run flag [test_id:7672should not unpaused 54] test_id:1599 : [sig-compute]VMIPreset Preset Matching [test_id:1599]Should return 404 if VMIPreset does not exist 55] test_id:3149 : infrastructure management [test_id:3149]should be able to create kubevirt install with image prefix 56] test_id:4612 : infrastructure management [test_id:4612]should create non-namespaces resources without owner references 57] test_id:1627 : should be able to boot from selected disk [test_id:1627]Alpine as first boot 58] test_id:1680 : when CPU model not defined [test_id:1680]should report CPU model from libvirt capabilities 59] test_id:3292 : with RHEL Template [test_id:3292]should succeed to create VirtualMachine via oc command 60] test_id:3293 : with RHEL Template [test_id:3293]should fail to delete VirtualMachine via oc command 61] test_id:3294 : with RHEL Template when the VirtualMachine was created [test_id:3294]should succeed to start the VirtualMachine via oc command 62] test_id:3295 : with RHEL Template when the VirtualMachine was created [test_id:3295]should succeed to delete VirtualMachine via oc command 63] test_id:3308 : with RHEL Template when the VirtualMachine was created [test_id:3308]should fail to create the same VirtualMachine via oc command 64] test_id:8607 : with TPM VMI option enabled [test_id:8607] should expose a functional emulated TPM which persists across migrations