flakefinder report for kubevirt/kubevirt

[sig-compute] Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus Endpoints [QUARANTINE]should include VMI infos for a running VM [test_id:4145] by IPv4

[sig-compute] Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus Endpoints [QUARANTINE]should include VMI infos for a running VM [test_id:6241] by IPv6

AfterSuite

VirtualMachineClone Tests VM clone [sig-compute]simple VM and cloning operations clone with changed MAC address

VirtualMachineClone Tests VM clone [sig-compute]simple VM and cloning operations clone with only some of labels/annotations

VirtualMachineClone Tests VM clone [sig-compute]simple VM and cloning operations clone with only some of template.labels/template.annotations

VirtualMachineClone Tests VM clone [sig-compute]simple VM and cloning operations regarding domain Firmware clone with changed SMBios serial

VirtualMachineClone Tests VM clone [sig-compute]simple VM and cloning operations regarding domain Firmware should strip firmware UUID

VirtualMachineClone Tests VM clone [sig-compute]simple VM and cloning operations simple clone with snapshot source, create clone before snapshot

VirtualMachineClone Tests VM clone [sig-compute]simple VM and cloning operations simple default clone

[rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Delete a VirtualMachineInstance with grace period greater than 0 [test_id:1655]should run graceful shutdown

[sig-compute] Infrastructure cluster profiler for pprof data aggregation when ClusterProfiler configuration is enabled it should allow subresource access

[sig-compute] Infrastructure virt-handler should enable/disable ksm and add/remove annotation on all the nodes when the selector is empty

[sig-compute] VMIDefaults MemBalloon defaults Should override period in domain if present in virt-config [test_id:4557]with period 12

[sig-compute]Configurations Custom PCI Addresses configuration should configure custom pci address [test_id:5269]across all available PCI root bus slots

[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with guestAgent with cluster config changes [test_id:5267]VMI condition should signal unsupported agent presence

[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with guestAgent with cluster config changes [test_id:6958]VMI condition should not signal unsupported agent presence for optional commands

[sig-compute]Configurations VirtualMachineInstance definition using defaultRuntimeClass configuration should apply runtimeClassName to pod when set

[sig-compute]Configurations VirtualMachineInstance definition with geust-to-request memory should add guest-to-memory headroom

[sig-compute]Configurations [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with CPU request settings [test_id:3129]should set CPU request from kubevirt-config

[sig-compute]Configurations [rfe_id:2869][crit:medium][vendor:cnv-qe@redhat.com][level:component]with machine type settings [test_id:3124]should set status.machine to the resolved QEMU machine type after VMI start

[sig-compute]Configurations [rfe_id:2869][crit:medium][vendor:cnv-qe@redhat.com][level:component]with machine type settings [test_id:3125]should allow creating VM without Machine defined

[sig-compute]Configurations [rfe_id:2869][crit:medium][vendor:cnv-qe@redhat.com][level:component]with machine type settings [test_id:3126]should set machine type from kubevirt-config

[sig-compute]Configurations [rfe_id:2869][crit:medium][vendor:cnv-qe@redhat.com][level:component]with machine type settings [test_id:6964]should allow creating VM defined with Machine with an empty Type

[sig-compute]Configurations [rfe_id:2926][crit:medium][vendor:cnv-qe@redhat.com][level:component]Check Chassis value [test_id:2927]Test Chassis value in a newly created VM

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning cpu pinning with fedora images, dedicated and non dedicated cpu should be possible on same node via spec.domain.cpu.cores [test_id:829]should start a vm with no cpu pinning after a vm with cpu pinning on same node

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning cpu pinning with fedora images, dedicated and non dedicated cpu should be possible on same node via spec.domain.cpu.cores [test_id:832]should start a vm with cpu pinning after a vm with no cpu pinning on same node

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:1685]non master node should have a cpumanager label

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:1688]should fail the vmi creation if the requested resources are inconsistent

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:1689]should fail the vmi creation if cpu is not an integer

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:1690]should fail the vmi creation if Guaranteed QOS cannot be set

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:4023]should start a vmi with dedicated cpus and isolated emulator thread with explicit resources set

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:4023]should start a vmi with dedicated cpus and isolated emulator thread without resource requirements set

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:4024]should fail the vmi creation if IsolateEmulatorThread requested without dedicated cpus

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:4632]should be able to start a vm with guest memory different from requested and keep guaranteed qos

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:802]should configure correct number of vcpus with requests.cpus

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:830]should start a vm with no cpu pinning after a vm with cpu pinning on same node

[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance with CPU pinning with cpu pinning enabled [test_id:991]should be scheduled on a node with running cpu manager

[sig-compute]Configurations with automatic CPU limit configured in the CR should not set a CPU limit if the namespace doesn't match the selector

[sig-compute]Configurations with automatic CPU limit configured in the CR should set a CPU limit if the namespace matches the selector

[sig-compute]Guest console log [level:component] Guest console log container fetch logs [QUARANTINE] it should fetch logs for a running VM with logs API

[sig-compute]VM state with persistent TPM VM option enabled should persist VM state of [test_id:10818]TPM across migration and restart

[sig-compute]VSOCK Live migration should retain the CID for migration target

[sig-compute]VSOCK VM creation should expose a VSOCK device Use virtio non-transitional

[sig-compute]VSOCK VM creation should expose a VSOCK device Use virtio transitional

[sig-compute]VSOCK communicating with VMI via VSOCK should succeed with TLS on both sides

[sig-compute]VSOCK communicating with VMI via VSOCK should succeed without TLS on both sides

[sig-compute]VSOCK should return err if no app listerns on the port

[sig-compute]VSOCK should return err if the port is invalid

[sig-network] VirtualMachineInstance with passt network binding plugin migration connectivity should be preserved [IPv6]

[sig-network] [crit:high][vendor:cnv-qe@redhat.com][level:component] [crit:high][vendor:cnv-qe@redhat.com][level:component]Creating a VirtualMachineInstance when virt-handler is responsive VMIs shouldn't fail after the kubelet restarts [sig-compute]with default networking

[sig-network] bridge nic-hotunplug a running VM hot-unplug network interface succeed Migration based

[sig-operator]Operator external CA should properly manage adding entries to the configmap

[sig-storage] Hotplug [storage-req] Online VM [QUARANTINE] should permanently add hotplug volume when added to VM, but still unpluggable after restart

[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated VM should restore a vm from an online snapshot with guest agent [test_id:6766] to the same VM