name: kubevirt-conformance
status: passed
meta:
  type: summary
items:
- name: junit.xml
  status: passed
  meta:
    file: results/global/junit.xml
    type: file
  items:
  - name: Tests Suite
    status: passed
    items:
    - name: '[sig-network] [crit:high][arm64][vendor:cnv-qe@redhat.com][level:component]
        [crit:high][vendor:cnv-qe@redhat.com][level:component]Creating a VirtualMachineInstance
        when virt-handler is responsive [Serial]VMIs shouldn''t fail after the kubelet
        restarts [sig-network]with bridge networking'
      status: skipped
    - name: '[sig-network] [crit:high][arm64][vendor:cnv-qe@redhat.com][level:component]
        [crit:high][vendor:cnv-qe@redhat.com][level:component]Creating a VirtualMachineInstance
        when virt-handler is responsive [Serial]VMIs shouldn''t fail after the kubelet
        restarts [sig-compute]with default networking'
      status: skipped
    - name: '[sig-network] [crit:high][arm64][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 with Bridge Networking should work with
        Duplicate Address Detection (DAD)'
      status: skipped
    - name: '[sig-compute]AMD Secure Encrypted Virtualization (SEV) [Serial]device
        management should reset SEV allocatable devices when the feature gate is disabled'
      status: skipped
    - name: '[sig-compute]AMD Secure Encrypted Virtualization (SEV) lifecycle should
        start a SEV or SEV-ES VM It should launch with base SEV features enabled'
      status: skipped
    - name: '[sig-compute]AMD Secure Encrypted Virtualization (SEV) lifecycle should
        start a SEV or SEV-ES VM It should launch with SEV-ES features enabled'
      status: skipped
    - name: '[sig-compute]AMD Secure Encrypted Virtualization (SEV) lifecycle should
        run guest attestation'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness should succeed [test_id:1202][posneg:positive]with
        working TCP probe and tcp server on ipv4'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness should succeed [test_id:1202][posneg:positive]with
        working TCP probe and tcp server on ipv6'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness should succeed [test_id:1200][posneg:positive]with
        working HTTP probe and http server on ipv4'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness should succeed [test_id:1200][posneg:positive]with
        working HTTP probe and http server on ipv6'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness should succeed [test_id:TODO]with
        working Exec probe'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness guest agent ping when
        the guest agent is enabled, after being disabled [test_id:6741] the VMI enters
        `Ready` state once again'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness should fail [test_id:1220][posneg:negative]with
        working TCP probe and no running server'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness should fail [test_id:1219][posneg:negative]with
        working HTTP probe and no running server'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness should fail [test_id:TODO]with
        working Exec probe and invalid command'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for readiness should fail [test_id:TODO]with
        working Exec probe and infinitely running command'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for liveness should not fail the VMI
        [test_id:1199][posneg:positive]with working TCP probe and tcp server on ipv4'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for liveness should not fail the VMI
        [test_id:1199][posneg:positive]with working TCP probe and tcp server on ipv6'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for liveness should not fail the VMI
        [test_id:1201][posneg:positive]with working HTTP probe and http server on
        ipv4'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for liveness should not fail the VMI
        [test_id:1201][posneg:positive]with working HTTP probe and http server on
        ipv6'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for liveness should not fail the VMI
        [test_id:5879]with working Exec probe'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for liveness guest agent ping [test_id:9299]
        VM stops when guest agent is disabled'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for liveness should fail the VMI [test_id:1217][posneg:negative]with
        working TCP probe and no running server'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for liveness should fail the VMI [test_id:1218][posneg:negative]with
        working HTTP probe and no running server'
      status: skipped
    - name: '[sig-network] [ref_id:1182]Probes for liveness should fail the VMI [test_id:5880]with
        working Exec probe and invalid command'
      status: skipped
    - name: '[rfe_id:127][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VNC
        [rfe_id:127][crit:medium][vendor:cnv-qe@redhat.com][level:component]A new
        VirtualMachineInstance with VNC connection [test_id:1611]should allow accessing
        the VNC device multiple times'
      status: skipped
    - name: '[rfe_id:127][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VNC
        [rfe_id:127][crit:medium][vendor:cnv-qe@redhat.com][level:component]A new
        VirtualMachineInstance [rfe_id:127][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        upgrade websocket connection which look like coming from a browser [test_id:1612]for
        vnc'
      status: skipped
    - name: '[rfe_id:127][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VNC
        [rfe_id:127][crit:medium][vendor:cnv-qe@redhat.com][level:component]A new
        VirtualMachineInstance [rfe_id:127][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        upgrade websocket connection which look like coming from a browser [test_id:1613]for
        serial console'
      status: skipped
    - name: '[rfe_id:127][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VNC
        [rfe_id:127][crit:medium][vendor:cnv-qe@redhat.com][level:component]A new
        VirtualMachineInstance [test_id:1614]should upgrade websocket connections
        without a subprotocol given'
      status: skipped
    - name: '[rfe_id:127][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VNC
        [rfe_id:127][crit:medium][vendor:cnv-qe@redhat.com][level:component]A new
        VirtualMachineInstance [test_id:4272]should connect to vnc with --proxy-only
        flag'
      status: skipped
    - name: '[rfe_id:127][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VNC
        [rfe_id:127][crit:medium][vendor:cnv-qe@redhat.com][level:component]A new
        VirtualMachineInstance [test_id:5274]should connect to vnc with --proxy-only
        flag to the specified port'
      status: skipped
    - name: '[rfe_id:127][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VNC
        [rfe_id:127][crit:medium][vendor:cnv-qe@redhat.com][level:component]A new
        VirtualMachineInstance should allow creating a VNC screenshot in PNG format'
      status: skipped
    - name: '[sig-compute]MultiQueue MultiQueue Behavior should be able to successfully
        boot fedora to the login prompt with multi-queue without being blocked by
        selinux [test_id:4599] with default virtio interface'
      status: skipped
    - name: '[sig-compute]MultiQueue MultiQueue Behavior should be able to successfully
        boot fedora to the login prompt with multi-queue without being blocked by
        selinux with e1000 interface'
      status: skipped
    - name: '[sig-compute]MultiQueue MultiQueue Behavior [test_id:959][rfe_id:2065]
        Should honor multiQueue requests'
      status: skipped
    - name: '[sig-compute]MultiQueue MultiQueue Behavior should be able to create
        a multi-queue VMI when requesting a single vCPU'
      status: skipped
    - name: '[sig-compute]IOThreads IOThreads Policies [test_id:4122]Should honor
        shared ioThreadsPolicy for single disk'
      status: skipped
    - name: '[sig-compute]IOThreads IOThreads Policies [test_id:864][ref_id:2065]
        Should honor a mix of shared and dedicated ioThreadsPolicy'
      status: skipped
    - name: '[sig-compute]IOThreads IOThreads Policies [ref_id:2065] should honor
        auto ioThreadPolicy [test_id:3097]for one CPU'
      status: skipped
    - name: '[sig-compute]IOThreads IOThreads Policies [ref_id:2065] should honor
        auto ioThreadPolicy [test_id:856] for two CPUs'
      status: skipped
    - name: '[sig-compute]IOThreads IOThreads Policies [ref_id:2065] should honor
        auto ioThreadPolicy [test_id:3095] for three CPUs'
      status: skipped
    - name: '[sig-compute]IOThreads IOThreads Policies [ref_id:2065] should honor
        auto ioThreadPolicy [test_id:3096]for four CPUs'
      status: skipped
    - name: '[sig-compute]IOThreads IOThreads Policies [test_id:4025]Should place
        io and emulator threads on the same pcpu with auto ioThreadsPolicy'
      status: skipped
    - name: '[Serial][sig-monitoring]Monitoring Kubevirt alert rules [test_id:8821]should
        have all the required annotations'
      status: skipped
    - name: '[Serial][sig-monitoring]Monitoring Kubevirt alert rules [test_id:8822]should
        have all the required labels'
      status: skipped
    - name: '[Serial][sig-monitoring]Monitoring Migration Alerts KubeVirtVMIExcessiveMigrations
        should be triggered when a VMI has been migrated more than 12 times during
        the last 24 hours'
      status: skipped
    - name: '[Serial][sig-monitoring]Monitoring System Alerts KubeVirtNoAvailableNodesToRunVMs
        should be triggered when there are no available nodes in the cluster to run
        VMs'
      status: skipped
    - name: '[Serial][sig-monitoring]Monitoring Deprecation Alerts KubeVirtDeprecatedAPIRequested
        should be triggered when a deprecated API is requested'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VMI [test_id:4597]should signal paused state with condition'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VMI [test_id:3224]should not be paused with a LivenessProbe configured'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VMI [test_id:7671]should not pause with dry run'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VMI [test_id:7672]should not unpause with dry run'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:4598]should signal paused state with condition'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:3081]should gracefully handle pausing the VM again'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:3060]should signal unpaused state with removed condition'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:3082]should gracefully handle unpausing again'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:3085]should be stopped successfully'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:3229]should gracefully handle being started again'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:3226]should be restarted successfully into unpaused state'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:3083]should connect to serial console'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:3084]should connect to vnc console'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:7673]should not pause with dry run'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        A valid VM [test_id:7674]should not unpause with dry run'
      status: skipped
    - name: '[rfe_id:3064][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Pausing
        Guest and Host uptime difference before pause [test_id:3090]should be less
        than uptime difference after pause'
      status: skipped
    - name: '[Serial][sig-compute]SecurityFeatures Check virt-launcher securityContext
        With selinuxLauncherType as container_t [test_id:2953]Ensure virt-launcher
        pod securityContext type is correctly set'
      status: skipped
    - name: '[Serial][sig-compute]SecurityFeatures Check virt-launcher securityContext
        With selinuxLauncherType as container_t [test_id:2895]Make sure the virt-launcher
        pod is not priviledged'
      status: skipped
    - name: '[Serial][sig-compute]SecurityFeatures Check virt-launcher securityContext
        With selinuxLauncherType as container_t [test_id:4297]Make sure qemu processes
        are MCS constrained'
      status: skipped
    - name: '[Serial][sig-compute]SecurityFeatures Check virt-launcher securityContext
        With selinuxLauncherType defined as spc_t [test_id:3787]Should honor custom
        SELinux type for virt-launcher'
      status: skipped
    - name: '[Serial][sig-compute]SecurityFeatures Check virt-launcher securityContext
        With selinuxLauncherType defined as virt_launcher.process [test_id:4298]qemu
        process type is virt_launcher.process, when selinuxLauncherType is virt_launcher.process'
      status: skipped
    - name: '[Serial][sig-compute]SecurityFeatures Check virt-launcher capabilities
        [test_id:4300]has precisely the documented extra capabilities relative to
        a regular user pod'
      status: skipped
    - name: '[Serial][sig-compute]SecurityFeatures Disabling the custom SELinux policy
        Should prevent virt-handler from installing the custom policy'
      status: skipped
    - name: '[Serial][sig-compute]SecurityFeatures The VMI SELinux context status
        Should get set and stay the the same after a migration'
      status: skipped
    - name: '[sig-storage] virtiofs VirtIO-FS with multiple PVCs [Serial] should be
        successfully started and accessible (privileged virtiofsd)'
      status: skipped
    - name: '[sig-storage] virtiofs VirtIO-FS with multiple PVCs [Serial] should be
        successfully started and accessible (unprivileged virtiofsd)'
      status: skipped
    - name: '[sig-storage] virtiofs VirtIO-FS with an empty PVC [Serial] should be
        successfully started and virtiofs could be accessed unprivileged virtiofsd'
      status: skipped
    - name: '[sig-storage] virtiofs VirtIO-FS with an empty PVC [Serial] should be
        successfully started and virtiofs could be accessed privileged virtiofsd'
      status: skipped
    - name: '[sig-storage] virtiofs Run a VMI with VirtIO-FS and a datavolume [Serial]
        should be successfully started and virtiofs could be accessed unprivileged
        virtiofsd'
      status: skipped
    - name: '[sig-storage] virtiofs Run a VMI with VirtIO-FS and a datavolume [Serial]
        should be successfully started and virtiofs could be accessed privileged virtiofsd'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Sound [crit:medium][vendor:cnv-qe@redhat.com][level:component] A VirtualMachineInstance
        with default sound support should create an ich9 sound device on empty model'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration with Headless service should remain to able resolve the
        VM IP'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a bridge network
        interface [test_id:3226]should reject a migration of a vmi with a bridge interface'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with bandwidth limitations
        [test_id:6968]should apply them and result in different migration durations'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk [test_id:6969]should
        be successfully migrate with a tablet device'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk should
        be successfully migrate with a WriteBack disk cache'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk [test_id:6970]should
        migrate vmi with cdroms on various bus types'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk should
        migrate vmi with LiveMigrateIfPossible eviction strategy'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk should
        migrate vmi and use Live Migration method with read-only disks'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk should
        migrate with a downwardMetrics [test_id:6971]disk'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk should
        migrate with a downwardMetrics channel'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk [test_id:6842]should
        migrate with TSC frequency set'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk [test_id:4113]should
        be successfully migrate with cloud-init disk with devices on the root bus'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk [test_id:9795]should
        migrate vmi with a usb disk'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk [test_id:1783]should
        be successfully migrated multiple times with cloud-init disk'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk [test_id:4746]should
        migrate even if virtqemud has restarted at some point.'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk [test_id:6972]should
        migrate to a persistent (non-transient) libvirt domain.'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a Alpine disk [test_id:6973]should
        be able to successfully migrate with a paused vmi'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with an pending target
        pod should automatically cancel unschedulable migration after a timeout period'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with an pending target
        pod should automatically cancel pending target pod after a catch all timeout
        period'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] with auto converge
        enabled [test_id:3237]should complete a migration'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with setting guest time
        [test_id:4114]should set an updated time after a migration'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with an Alpine DataVolume
        [test_id:3239]should reject a migration of a vmi with a non-shared data volume'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with an Alpine DataVolume
        [test_id:1479][storage-req] should migrate a vmi with a shared block disk'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with an Alpine DataVolume
        [test_id:6974]should reject additional migrations on the same VMI if the first
        one is not finished'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [storage-req]with an
        Alpine shared block volume PVC [test_id:1854]should migrate a VMI with shared
        and non-shared disks'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [storage-req]with an
        Alpine shared block volume PVC [release-blocker][test_id:1377]should be successfully
        migrated multiple times'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [storage-req]with an
        Alpine shared block volume PVC [test_id:3240]should be successfully with a
        cloud init'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        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'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        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'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration to
        nonroot should migrate root implementation to nonroot [test_id:8609] with
        simple VMI'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration to
        nonroot should migrate root implementation to nonroot [test_id:8610] with
        DataVolume'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration to
        nonroot should migrate root implementation to nonroot [test_id:8611] with
        CD + CloudInit + SA + ConfigMap + Secret + DownwardAPI + Kernel Boot'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration to
        nonroot should migrate root implementation to nonroot [test_id:8612] with
        PVC'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration to
        root should migrate nonroot implementation to root with simple VMI'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration to
        root should migrate nonroot implementation to root with DataVolume'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration to
        root should migrate nonroot implementation to root with CD + CloudInit + SA
        + ConfigMap + Secret + DownwardAPI + Kernel Boot'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration to
        root should migrate nonroot implementation to root with PVC'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  migration security [Serial]
        with TLS disabled [test_id:6976] should be successfully migrated'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  migration security [Serial]
        with TLS disabled [test_id:6977]should not secure migrations with TLS'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  migration security with
        TLS enabled [test_id:2303][posneg:negative] should secure migrations with
        TLS'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration monitor
        without progress [test_id:2227] should abort a vmi migration'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration monitor
        [test_id:6978] Should detect a failed migration'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration monitor
        old finalized migrations should get garbage collected'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration monitor
        [test_id:6979]Target pod should exit after failed migration'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration monitor
        [test_id:6980]Migration should fail if target pod fails during target preparation'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] migration monitor
        Migration should generate empty isos of the right size on the target'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [storage-req]with an
        Alpine non-shared block volume PVC [test_id:1862][posneg:negative]should reject
        migrations for a non-migratable vmi'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  live migration cancelation
        should be able to cancel a migration [sig-storage][test_id:2226] with ContainerDisk'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  live migration cancelation
        should be able to cancel a migration [sig-storage][storage-req][test_id:2731]
        with RWX block disk from block volume PVC'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  live migration cancelation
        [sig-compute][test_id:3241]Immediate migration cancellation after migration
        starts running cancel a migration by deleting vmim object'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  live migration cancelation
        [sig-compute][test_id:8584]Immediate migration cancellation before migration
        starts running cancel a migration by deleting vmim object'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  live migration cancelation
        [Serial]when target pod cannot be scheduled and is suck in Pending phase should
        be able to properly abort migration'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a host-model cpu
        [test_id:6981]should migrate only to nodes supporting right cpu model'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a host-model cpu
        [Serial]Should trigger event if vmi with host-model start on source node with
        uniq host-model [test_id:7505]when no node is suited for host model'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  with a host-model cpu
        [Serial]Should trigger event if the nodes doesn''t contain MigrationSelectorLabel
        for the vmi host-model type no node contain suited SupportedHostModelMigrationCPU
        label'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  parallel migration threads
        should run successfully when configured through a VMI annotation'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] with migration
        policies migration policy should override cluster-wide policy if defined'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] with migration
        policies migration policy should not affect cluster-wide policy if not defined'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration Starting a VirtualMachineInstance  [Serial] with freePageReporting
        should be able to migrate'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration with sata disks [test_id:1853]VM with containerDisk + CloudInit
        + ServiceAccount + ConfigMap + Secret + DownwardAPI + External Kernel Boot
        + USB Disk'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration [test_id:8482] Migration Metrics exposed to prometheus during
        VM migration'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration [Serial] With Huge Pages should consume hugepages  [test_id:6983]hugepages-2Mi'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration [Serial] With Huge Pages should consume hugepages  [test_id:6984]hugepages-1Gi'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration [Serial] with CPU pinning and huge pages should not make
        migrations fail'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration [Serial] with CPU pinning and huge pages and NUMA passthrough
        should not make migrations fail'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration [Serial]Testing host-model cpuModel edge cases in the cluster
        if the cluster is host-model migratable Should be able to migrate back to
        the initial node from target node with host-model even if target is newer
        than source'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration [Serial]Testing host-model cpuModel edge cases in the cluster
        if the cluster is host-model migratable vmi with host-model should be able
        to migrate to node that support the initial node''s host-model even if this
        model isn''t the target''s host-model'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration with dedicated CPUs should successfully update a VMI''s
        CPU set on migration'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration [Serial] with a dedicated migration network Should migrate
        over that network'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration should update MigrationState''s MigrationConfiguration of
        VMI status'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration with a live-migration in flight there should always be a
        single active migration per VMI'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration topology hints needs to be set when invtsc feature exists'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration topology hints needs to be set when HyperV reenlightenment
        is enabled'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration during evacuation should add eviction-in-progress annotation
        to source virt-launcher pod'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration during evacuation when evacuating fails should remove eviction-in-progress
        annotation to source virt-launcher pod'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration during evacuation when evacuating fails retrying immediately
        should be blocked by the migration backoff'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration during evacuation when evacuating fails after a successful
        migration backoff should be cleared'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Live Migration ResourceQuota rejection Should contain condition when migrating
        with quota that doesn''t have resources for both source and target'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [storage-req]PVC expansion PVC expansion
        is detected by VM and can be fully used with Block PVC'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [storage-req]PVC expansion PVC expansion
        is detected by VM and can be fully used with Filesystem PVC'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [storage-req]PVC expansion Check
        disk expansion accounts for actual usable size'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachineInstance with a DataVolume as a volume source [Serial]without
        fsgroup support should succesfully start'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachineInstance with a DataVolume as a volume source Alpine
        import [test_id:3189]should be successfully started and stopped multiple times'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachineInstance with a DataVolume as a volume source Alpine
        import [test_id:6686]should successfully start multiple concurrent VMIs'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachineInstance with a DataVolume as a volume source Alpine
        import [test_id:5252]should be successfully started when using a PVC volume
        owned by a DataVolume'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachineInstance with a DataVolume as a volume source Alpine
        import should accurately aggregate DataVolume conditions from many DVs'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachineInstance with a DataVolume as a volume source with
        a PVC from a Datavolume [test_id:4643]should NOT be rejected when VM template
        lists a DataVolume, but VM lists PVC VolumeSource'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachine with an invalid DataVolume using DataVolume with
        invalid URL should be possible to stop VM if datavolume is crashing'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachine with an invalid DataVolume using DataVolume with
        invalid URL [test_id:3190]should correctly handle invalid DataVolumes'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachine with an invalid DataVolume using DataVolume with
        invalid URL [test_id:3190]should correctly handle eventually consistent DataVolumes'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:896][crit:high][vendor:cnv-qe@redhat.com][level:system]
        with oc/kubectl [test_id:836] Creating a VM with DataVolumeTemplates should
        succeed.'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:896][crit:high][vendor:cnv-qe@redhat.com][level:system]
        with oc/kubectl [test_id:837]deleting VM with cascade=true should automatically
        delete DataVolumes and VMI owned by VM.'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:896][crit:high][vendor:cnv-qe@redhat.com][level:system]
        with oc/kubectl [test_id:838]deleting VM with cascade=false should orphan
        DataVolumes and VMI owned by VM.'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachine with a DataVolume using Alpine http import [test_id:3191]should
        be successfully started and stopped multiple times'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Starting a VirtualMachine with a DataVolume using Alpine http import [test_id:3192]should
        remove owner references on DataVolume if VM is orphan deleted.'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone should resolve
        DataVolume sourceRef with PVC source'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone should resolve
        DataVolume sourceRef with Snapshot source'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone should report
        DataVolume without source PVC'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone [storage-req]
        deny then allow clone request [test_id:3193]with explicit role'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone [storage-req]
        deny then allow clone request [test_id:3194]with implicit role'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone [storage-req]
        deny then allow clone request [test_id:5253]with explicit role (all namespaces)'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone [storage-req]
        deny then allow clone request [test_id:5254]with explicit role (one namespace)'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone [storage-req]
        deny then allow clone request with explicit role snapshot clone'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone [storage-req]
        deny then allow clone request with implicit insufficient role snapshot clone'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone [storage-req]
        deny then allow clone request with implicit sufficient role snapshot clone'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone [storage-req]
        deny then allow clone request with explicit role (all namespaces) snapshot
        clone'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone [storage-req]
        deny then allow clone request with explicit role (one namespace) snapshot
        clone'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [rfe_id:3188][crit:high][vendor:cnv-qe@redhat.com][level:system]
        DataVolume clone permission checking using Alpine import/clone should skip
        authorization when DataVolume already exists'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [Serial][rfe_id:8400][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Garbage collection of succeeded DV Verify DV of VM with DataVolumeTemplates
        is garbage collected when [test_id:8567]GC is enabled'
      status: skipped
    - name: '[sig-storage] DataVolume Integration [Serial][rfe_id:8400][crit:high][vendor:cnv-qe@redhat.com][level:system]
        Garbage collection of succeeded DV Verify DV of VM with DataVolumeTemplates
        is garbage collected when [test_id:8571]GC is disabled, and after VM creation,
        GC is enabled and DV is annotated'
      status: skipped
    - name: '[sig-storage] DataVolume Integration Fedora VMI tests [rfe_id:5070][crit:medium][vendor:cnv-qe@redhat.com][level:component]fstrim
        from the VM influences disk.img [test_id:5894]by default, fstrim will make
        the image smaller'
      status: skipped
    - name: '[sig-storage] DataVolume Integration Fedora VMI tests [rfe_id:5070][crit:medium][vendor:cnv-qe@redhat.com][level:component]fstrim
        from the VM influences disk.img [test_id:5898]with preallocation true, fstrim
        has no effect'
      status: skipped
    - name: '[sig-storage] DataVolume Integration Fedora VMI tests [rfe_id:5070][crit:medium][vendor:cnv-qe@redhat.com][level:component]fstrim
        from the VM influences disk.img [test_id:5897]with preallocation false, fstrim
        will make the image smaller'
      status: skipped
    - name: '[sig-storage] DataVolume Integration Fedora VMI tests [rfe_id:5070][crit:medium][vendor:cnv-qe@redhat.com][level:component]fstrim
        from the VM influences disk.img [test_id:5899]with thick provision true, fstrim
        has no effect'
      status: skipped
    - name: '[sig-storage] DataVolume Integration Fedora VMI tests [rfe_id:5070][crit:medium][vendor:cnv-qe@redhat.com][level:component]fstrim
        from the VM influences disk.img [test_id:5896]with thick provision false,
        fstrim will make the image smaller'
      status: skipped
    - name: '[sig-storage] DataVolume Integration With VirtualMachinePreference and
        PreferredStorageClassName should use PreferredStorageClassName when storage
        class not provided by VM'
      status: skipped
    - name: '[sig-storage] DataVolume Integration With VirtualMachinePreference and
        PreferredStorageClassName should always use VM defined storage class over
        PreferredStorageClassName'
      status: skipped
    - name: '[sig-network] Services bridge interface binding with a service matching
        the vmi exposed [test_id:1547] should be able to reach the vmi based on labels
        specified on the vmi'
      status: skipped
    - name: '[sig-network] Services bridge interface binding with a service matching
        the vmi exposed [test_id:1548] should fail to reach the vmi if an invalid
        servicename is used'
      status: skipped
    - name: '[sig-network] Services bridge interface binding with a subdomain and
        a headless service given [test_id:1549]should be able to reach the vmi via
        its unique fully qualified domain name'
      status: skipped
    - name: '[sig-network] Services Masquerade interface binding with a service matching
        the vmi exposed [Conformance] should be able to reach the vmi based on labels
        specified on the vmi when the service is exposed by an IPv4 address.'
      status: passed
    - name: '[sig-network] Services Masquerade interface binding with a service matching
        the vmi exposed [Conformance] should be able to reach the vmi based on labels
        specified on the vmi when the service is exposed by an IPv6 address.'
      status: skipped
    - name: '[sig-network] Services Masquerade interface binding *without* a service
        matching the vmi exposed should fail to reach the vmi'
      status: skipped
    - name: '[sig-network] [Serial] SRIOV nic-hotplug a running VM can hotplug a network
        interface'
      status: skipped
    - name: '[sig-compute]VMI with external kernel boot with external alpine-based
        kernel & initrd images [test_id:7748]ensure successful boot'
      status: skipped
    - name: '[sig-compute]VMI with external kernel boot with external alpine-based
        kernel & initrd images ensure successful boot and deletion when VMI has a
        disk defined'
      status: skipped
    - name: '[sig-compute]VMI with external kernel boot with illegal definition ensure
        rejection of [test_id:7750]VMI defined without an image'
      status: skipped
    - name: '[sig-compute]VMI with external kernel boot with illegal definition ensure
        rejection of [test_id:7751]VMI defined with image but without initrd & kernel
        paths'
      status: skipped
    - name: '[sig-compute]VMI with external kernel boot with external alpine-based
        kernel only (without initrd) ensure successful boot'
      status: skipped
    - name: '[sig-compute]VMI with external kernel boot with external alpine-based
        kernel only (without initrd) ensure successful boot and deletion when VMI
        has a disk defined'
      status: skipped
    - name: '[sig-compute] Guest Access Credentials should have ssh-key under authorized
        keys added [test_id:6220] using qemu guest agent'
      status: skipped
    - name: '[sig-compute] Guest Access Credentials should have ssh-key under authorized
        keys added [test_id:6224] using configdrive'
      status: skipped
    - name: '[sig-compute] Guest Access Credentials should have ssh-key under authorized
        keys added using nocloud'
      status: skipped
    - name: '[sig-compute] Guest Access Credentials with qemu guest agent [test_id:6221]should
        propagate user password'
      status: skipped
    - name: '[sig-compute] Guest Access Credentials with qemu guest agent should update
        to unsupported agent [test_id:6222]for public ssh keys'
      status: skipped
    - name: '[sig-compute] Guest Access Credentials with qemu guest agent should update
        to unsupported agent [test_id:6223] for user password'
      status: skipped
    - name: '[Serial][ref_id:2717][sig-compute]KubeVirt control plane resilience pod
        eviction evicting pods of control plane [test_id:2830]last eviction should
        fail for multi-replica virt-controller pods'
      status: skipped
    - name: '[Serial][ref_id:2717][sig-compute]KubeVirt control plane resilience pod
        eviction evicting pods of control plane [test_id:2799]last eviction should
        fail for multi-replica virt-api pods'
      status: skipped
    - name: '[Serial][ref_id:2717][sig-compute]KubeVirt control plane resilience pod
        eviction evicting pods of control plane eviction of single-replica virt-controller
        pod should succeed'
      status: skipped
    - name: '[Serial][ref_id:2717][sig-compute]KubeVirt control plane resilience pod
        eviction evicting pods of control plane eviction of multi-replica virt-api
        pod should succeed'
      status: skipped
    - name: '[Serial][ref_id:2717][sig-compute]KubeVirt control plane resilience control
        plane components check when control plane pods are running [test_id:2806]virt-controller
        and virt-api pods have a pod disruption budget'
      status: skipped
    - name: '[Serial][ref_id:2717][sig-compute]KubeVirt control plane resilience control
        plane components check when Control plane pods temporarily lose connection
        to Kubernetes API should fail health checks when connectivity is lost, and
        recover when connectivity is regained'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1195][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        Rbac Authorization with correct permissions [test_id:3170]should be allowed
        to access subresource endpoint'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1195][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        Rbac Authorization Without permissions [test_id:3171]should not be able to
        access subresource endpoint'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1195][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        Rbac Authorization For Version Command with authenticated user [test_id:3172]should
        be allowed to access subresource version endpoint'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1195][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        Rbac Authorization For Version Command Without permissions [test_id:3173]should
        be able to access subresource version endpoint'
      status: skipped
    - name: '[sig-compute]Subresource Api [crit:medium][vendor:cnv-qe@redhat.com][level:component]
        Rbac Authorization For Guestfs Command with authenticated user should be allowed
        to access subresource guestfs endpoint'
      status: skipped
    - name: '[sig-compute]Subresource Api [crit:medium][vendor:cnv-qe@redhat.com][level:component]
        Rbac Authorization For Guestfs Command Without permissions should be able
        to access subresource guestfs endpoint'
      status: skipped
    - name: '[sig-compute]Subresource Api [crit:medium][vendor:cnv-qe@redhat.com][level:component]
        Rbac Authorization For Expand-Spec Command should be allowed to access expand-vm-spec
        endpoint with authenticated user'
      status: skipped
    - name: '[sig-compute]Subresource Api [crit:medium][vendor:cnv-qe@redhat.com][level:component]
        Rbac Authorization For Expand-Spec Command should not be able to access expand-vm-spec
        endpoint without authenticated user'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VirtualMachine subresource with a restart endpoint should return an error
        when VM is not running [test_id:1305][posneg:negative] with RunStrategyHalted'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VirtualMachine subresource with a restart endpoint should return an error
        when VM is not running [test_id:3174] with RunStrategyManual'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VirtualMachine subresource with a restart endpoint [test_id:2265][posneg:negative]
        should return an error when VM has not been found but VMI is running'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VirtualMachine subresource [test_id:1529]should start a VirtualMachine only
        once'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VirtualMachine subresource [test_id:1530]should stop a VirtualMachine only
        once'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VirtualMachine subresource [test_id:3007][QUARANTINE] Should force restart
        a VM with terminationGracePeriodSeconds>0'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VirtualMachine subresource should force stop a VM with terminationGracePeriodSeconds>0'
      status: skipped
    - name: '[sig-compute]Subresource Api [rfe_id:1195][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        the openapi spec for the subresources [test_id:3177]should be aggregated into
        the apiserver openapi spec'
      status: skipped
    - name: '[sig-compute]Subresource Api VirtualMachineInstance subresource Freeze
        Unfreeze should fail [test_id:7476]Freeze without guest agent'
      status: skipped
    - name: '[sig-compute]Subresource Api VirtualMachineInstance subresource Freeze
        Unfreeze should fail [test_id:7477]Unfreeze without guest agent'
      status: skipped
    - name: '[sig-compute]Subresource Api VirtualMachineInstance subresource Freeze
        Unfreeze commands [test_id:7479]Freeze Unfreeze should succeed'
      status: skipped
    - name: '[sig-compute]Subresource Api VirtualMachineInstance subresource Freeze
        Unfreeze commands [test_id:7480]Multi Freeze Unfreeze calls should succeed'
      status: skipped
    - name: '[sig-compute]Subresource Api VirtualMachineInstance subresource Freeze
        Unfreeze commands Freeze without Unfreeze should trigger unfreeze after timeout'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        existing VM [test_id:TODO] should return unchanged VirtualMachine, if instancetype
        is not used'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        existing VM [test_id:TODO] should return VirtualMachine with instancetype
        expanded with VirtualMachineInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        existing VM [test_id:TODO] should return VirtualMachine with instancetype
        expanded with VirtualMachineClusterInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        passed VM in request [test_id:TODO] should return unchanged VirtualMachine,
        if instancetype is not used'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        passed VM in request [test_id:TODO] should return VirtualMachine with instancetype
        expanded with VirtualMachineInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        passed VM in request [test_id:TODO] should return VirtualMachine with instancetype
        expanded with VirtualMachineClusterInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        passed VM in request [test_id:TODO] should fail, if referenced instancetype
        does not exist with VirtualMachineInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        passed VM in request [test_id:TODO] should fail, if referenced instancetype
        does not exist with VirtualMachineClusterInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        passed VM in request [test_id:TODO] should fail, if instancetype expansion
        hits a conflict with VirtualMachineInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        passed VM in request [test_id:TODO] should fail, if instancetype expansion
        hits a conflict with VirtualMachineClusterInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        passed VM in request [test_id:TODO] should fail, if VM and endpoint namespace
        are different with VirtualMachineInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource instancetype with
        passed VM in request [test_id:TODO] should fail, if VM and endpoint namespace
        are different with VirtualMachineClusterInstancetype'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource preference with existing
        VM [test_id:TODO] should return unchanged VirtualMachine, if preference is
        not used'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource preference with existing
        VM [test_id:TODO] should return VirtualMachine with preference expanded with
        VirtualMachinePreference'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource preference with existing
        VM [test_id:TODO] should return VirtualMachine with preference expanded with
        VirtualMachineClusterPreference'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource preference with passed
        VM in request [test_id:TODO] should return unchanged VirtualMachine, if preference
        is not used'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource preference with passed
        VM in request [test_id:TODO] should return VirtualMachine with preference
        expanded with VirtualMachinePreference'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource preference with passed
        VM in request [test_id:TODO] should return VirtualMachine with preference
        expanded with VirtualMachineClusterPreference'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource preference with passed
        VM in request [test_id:TODO] should fail, if referenced preference does not
        exist with VirtualMachinePreference'
      status: skipped
    - name: '[sig-compute]Subresource Api ExpandSpec subresource preference with passed
        VM in request [test_id:TODO] should fail, if referenced preference does not
        exist with VirtualMachineClusterPreference'
      status: skipped
    - name: '[sig-compute]virt-handler [Serial] multiple HTTP calls should re-use
        connections and not grow the number of open connections'
      status: skipped
    - name: '[Serial][sig-compute]MediatedDevices with externally provided mediated
        devices Should make sure that mdevs listed with ExternalResourceProvider are
        not removed'
      status: skipped
    - name: '[Serial][sig-compute]MediatedDevices with externally provided mediated
        devices Should make sure that no mdev is removed if the feature is gated'
      status: skipped
    - name: '[Serial][sig-compute]MediatedDevices with mediated devices configuration
        Should successfully passthrough a mediated device'
      status: skipped
    - name: '[Serial][sig-compute]MediatedDevices with mediated devices configuration
        Should successfully passthrough a mediated device with a disabled display'
      status: skipped
    - name: '[Serial][sig-compute]MediatedDevices with mediated devices configuration
        Should override default mdev configuration on a specific node'
      status: skipped
    - name: '[Serial][sig-compute]MediatedDevices with generic mediated devices should
        create mdevs on devices that appear after CR configuration'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-compute]simple VM and
        cloning operations simple default clone'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-compute]simple VM and
        cloning operations simple clone with snapshot source'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-compute]simple VM and
        cloning operations clone with only some of labels/annotations'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-compute]simple VM and
        cloning operations clone with only some of template.labels/template.annotations'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-compute]simple VM and
        cloning operations clone with changed MAC address'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-compute]simple VM and
        cloning operations regarding domain Firmware clone with changed SMBios serial'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-compute]simple VM and
        cloning operations regarding domain Firmware should strip firmware UUID'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-storage]with more complicated
        VM and no snapshot storage class should reject source with non snapshotable
        volume with VM source'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-storage]with more complicated
        VM and no snapshot storage class should reject source with non snapshotable
        volume with snapshot source'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-storage]with more complicated
        VM and snapshot storage class with a simple clone'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-storage]with more complicated
        VM and snapshot storage class with instancetype and preferences should create
        new ControllerRevisions for cloned VM with a running VM'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-storage]with more complicated
        VM and snapshot storage class with instancetype and preferences should create
        new ControllerRevisions for cloned VM with a stopped VM'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-storage]with more complicated
        VM and snapshot storage class double cloning: clone target as a clone source'
      status: skipped
    - name: '[Serial]VirtualMachineClone Tests VM clone [sig-storage]with more complicated
        VM and snapshot storage class with WaitForFirstConsumer binding mode should
        not delete the vmsnapshot and vmrestore until all the pvc(s) are bound'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure changes to the kubernetes client
        on the controller rate limiter should lead to delayed VMI starts'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure changes to the kubernetes client
        on the virt handler rate limiter should lead to delayed VMI running states'
      status: skipped
    - name: '[sig-compute]VM state with persistent TPM VM option enabled should persist
        VM state of [test_id:10818]TPM across migration and restart'
      status: skipped
    - name: '[sig-compute]VM state with persistent TPM VM option enabled should persist
        VM state of [test_id:10819]TPM across restart and migration'
      status: skipped
    - name: '[sig-compute]VM state with persistent TPM VM option enabled should persist
        VM state of [test_id:10820]EFI across migration and restart'
      status: skipped
    - name: '[sig-compute]VM state with persistent TPM VM option enabled should persist
        VM state of [test_id:10821]TPM+EFI across migration and restart'
      status: skipped
    - name: '[sig-compute]VM state with persistent TPM VM option enabled should persist
        VM state of TPM across migration and restart'
      status: skipped
    - name: '[sig-compute]VM state with persistent TPM VM option enabled should persist
        VM state of TPM across restart and migration'
      status: skipped
    - name: '[sig-compute]VM state with persistent TPM VM option enabled should persist
        VM state of EFI across migration and restart'
      status: skipped
    - name: '[sig-compute]VM state with persistent TPM VM option enabled should persist
        VM state of TPM+EFI across migration and restart'
      status: skipped
    - name: '[sig-compute]VM state with persistent TPM VM option enabled should remove
        persistent storage PVC if VMI is not owned by a VM'
      status: skipped
    - name: '[sig-network] Subdomain with a headless service given VMI should have
        the expected FQDN with Masquerade binding and subdomain and hostname'
      status: skipped
    - name: '[sig-network] Subdomain with a headless service given VMI should have
        the expected FQDN with Bridge binding and subdomain'
      status: skipped
    - name: '[sig-network] Subdomain with a headless service given VMI should have
        the expected FQDN with Masquerade binding without subdomain'
      status: skipped
    - name: '[sig-network] Subdomain with a headless service given VMI should have
        the expected FQDN with Bridge binding without subdomain'
      status: skipped
    - name: '[sig-network] Subdomain with a headless service given VMI with custom
        DNSPolicy should have the expected FQDN'
      status: skipped
    - name: '[sig-network] Subdomain VMI with custom DNSPolicy, a subdomain and no
        service entry, should not include the subdomain in the searchlist'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure CRDs [test_id:5177]Should have structural
        schema'
      status: skipped
    - name: '[rfe_id:899][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Config
        With a ConfigMap defined With a single volume [test_id:782]Should be the fs
        layout the same for a pod and vmi'
      status: skipped
    - name: '[rfe_id:899][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Config
        With a ConfigMap defined With multiple volumes [test_id:783]Should start VMI
        with multiple ConfigMaps'
      status: skipped
    - name: '[rfe_id:899][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Config
        With a Secret defined With a single volume [test_id:779]Should be the fs layout
        the same for a pod and vmi'
      status: skipped
    - name: '[rfe_id:899][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Config
        With a Secret defined With multiple volumes [test_id:780]Should start VMI
        with multiple Secrets'
      status: skipped
    - name: '[rfe_id:899][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Config
        With a ServiceAccount defined [test_id:998]Should be the namespace and token
        the same for a pod and vmi'
      status: skipped
    - name: '[rfe_id:899][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Config
        With a Secret and a ConfigMap defined With a single volume [test_id:786]Should
        be that cfgMap and secret fs layout same for the pod and vmi'
      status: skipped
    - name: '[rfe_id:899][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Config
        With SSH Keys as a Secret defined With a single volume [test_id:778]Should
        be the fs layout the same for a pod and vmi'
      status: skipped
    - name: '[rfe_id:899][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Config
        With a DownwardAPI defined [test_id:790]Should be the namespace and token
        the same for a pod and vmi'
      status: skipped
    - name: '[sig-compute]vTPM [rfe_id:5168][crit:high][vendor:cnv-qe@redhat.com][level:component]
        with TPM VMI option enabled [test_id:8607] should expose a functional emulated
        TPM which persists across migrations'
      status: skipped
    - name: '[sig-network] Dual stack cluster network configuration when dual stack
        cluster configuration is enabled the cluster must be dual stack'
      status: skipped
    - name: '[sig-storage] Hotplug Offline VM Should add volumes on an offline VM
        with DataVolume'
      status: skipped
    - name: '[sig-storage] Hotplug Offline VM Should add volumes on an offline VM
        with PersistentVolume'
      status: skipped
    - name: '[sig-storage] Hotplug Offline VM with a block volume Should start with
        a hotplug block DataVolume'
      status: skipped
    - name: '[sig-storage] Hotplug Offline VM with a block volume Should start with
        a hotplug block PersistentVolume'
      status: skipped
    - name: '[sig-storage] Hotplug Offline VM with a block volume [Serial]Should preserve
        access to block devices if virt-handler crashes'
      status: skipped
    - name: '[sig-storage] Hotplug WFFC storage Should be able to add and use WFFC
        local storage'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should add/remove volume
        with DataVolume immediate attach'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should add/remove volume
        with PersistentVolume immediate attach'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should add/remove volume
        with DataVolume wait for VM to finish starting'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should add/remove volume
        with PersistentVolume wait for VM to finish starting'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should add/remove volume
        with DataVolume immediate attach, VMI directly'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should add/remove volume
        with PersistentVolume immediate attach, VMI directly'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should add/remove volume
        with Block DataVolume immediate attach'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should not add/remove volume
        with dry run with DataVolume immediate attach'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should not add/remove volume
        with dry run with PersistentVolume immediate attach'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should not add/remove volume
        with dry run with DataVolume immediate attach, VMI directly'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should not add/remove volume
        with dry run with PersistentVolume immediate attach, VMI directly'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should not add/remove volume
        with dry run with Block DataVolume immediate attach'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM Should be able to add and
        remove multiple volumes with VMs'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM Should be able to add and
        remove multiple volumes with VMIs'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM Should be able to add and
        remove multiple volumes with VMs and block'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM Should be able to add and
        remove and re-add multiple volumes with VMs'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM Should be able to add and
        remove and re-add multiple volumes with VMIs'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM Should be able to add and
        remove and re-add multiple volumes [Serial] with VMs and block'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should allow to hotplug
        75 volumes simultaneously'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should permanently add
        hotplug volume when added to VM, but still unpluggable after restart'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should reject hotplugging
        a volume with the same name as an existing volume'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should reject hotplugging
        the same volume with an existing volume name'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should reject removing
        a volume which wasn''t hotplugged'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should reject removing
        a volume which doesn''t exist'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] Online VM should allow hotplugging
        both a filesystem and block volume'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] VMI migration should allow live migration
        with attached hotplug volumes containerDisk VMI'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] VMI migration should allow live migration
        with attached hotplug volumes persistent disk VMI'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] disk mutating sidecar should be able
        to add and remove volumes with DataVolume and running VM'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] disk mutating sidecar should be able
        to add and remove volumes with DataVolume and VMI directly'
      status: skipped
    - name: '[sig-storage] Hotplug [storage-req] disk mutating sidecar should be able
        to add and remove volumes [Serial] with Block DataVolume immediate attach'
      status: skipped
    - name: '[sig-storage] Hotplug delete attachment pod several times should remain
        active'
      status: skipped
    - name: '[sig-storage] Hotplug with limit range in namespace hotplug volume should
        have mem ratio same as VMI with limit range applied [test_id:10002][Serial]1
        to 1 cpu and mem ratio'
      status: skipped
    - name: '[sig-storage] Hotplug with limit range in namespace hotplug volume should
        have mem ratio same as VMI with limit range applied [test_id:10003]Serial]1
        to 1 mem ratio, 4 to 1 cpu ratio'
      status: skipped
    - name: '[sig-storage] Hotplug with limit range in namespace hotplug volume should
        have mem ratio same as VMI with limit range applied [test_id:10004][Serial]2
        to 1 mem ratio, 4 to 1 cpu ratio'
      status: skipped
    - name: '[sig-storage] Hotplug with limit range in namespace hotplug volume should
        have mem ratio same as VMI with limit range applied [test_id:10005][Serial]2.25
        to 1 mem ratio, 5.75 to 1 cpu ratio'
      status: skipped
    - name: '[sig-storage] Hotplug hostpath should attach a hostpath based volume
        to running VM'
      status: skipped
    - name: '[sig-storage] Hotplug iothreads should allow adding and removing hotplugged
        volumes'
      status: skipped
    - name: '[sig-storage] Hotplug hostpath-separate-device should attach a hostpath
        based volume to running VM'
      status: skipped
    - name: '[sig-storage] Hotplug [Serial]Hotplug LUN disk on an offline VM'
      status: skipped
    - name: '[sig-storage] Hotplug [Serial]Hotplug LUN disk on an online VM'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Live Migration All containers should complete in
        source virt-launcher pod after migration'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface SSH traffic With VMI having explicit ports specified
        should ssh to VMI with Istio proxy'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface SSH traffic With VMI having no explicit ports specified
        should ssh to VMI with Istio proxy'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Inbound traffic With VMI having explicit ports specified
        request to VMI should reach HTTP server on service declared port on VMI with
        explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Inbound traffic With VMI having explicit ports specified
        request to VMI should reach HTTP server on service undeclared port on VMI
        with explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Inbound traffic With VMI having no explicit ports
        specified request to VMI should reach HTTP server on service declared port
        on VMI with no explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Inbound traffic With VMI having no explicit ports
        specified request to VMI should reach HTTP server on service undeclared port
        on VMI with no explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Inbound traffic With VMI having no explicit ports
        specified Should not be able to reach service running on Istio restricted
        port'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Inbound traffic With PeerAuthentication enforcing
        mTLS With VMI having explicit ports specified client outside mesh should NOT
        reach VMI HTTP server on service declared port on VMI with explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Inbound traffic With PeerAuthentication enforcing
        mTLS With VMI having explicit ports specified client outside mesh should NOT
        reach VMI HTTP server on service undeclared port on VMI with explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Inbound traffic With PeerAuthentication enforcing
        mTLS With VMI having no explicit ports specified client outside mesh should
        NOT reach VMI HTTP server on service declared port on VMI with no explicit
        ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Inbound traffic With PeerAuthentication enforcing
        mTLS With VMI having no explicit ports specified client outside mesh should
        NOT reach VMI HTTP server on service undeclared port on VMI with no explicit
        ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Outbound traffic VMI with explicit ports Should
        be able to reach http server outside of mesh'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Outbound traffic VMI with no explicit ports Should
        be able to reach http server outside of mesh'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Outbound traffic With Sidecar allowing only registered
        external services VMI with explicit ports Should not be able to reach http
        service outside of mesh'
      status: skipped
    - name: '[sig-network] [Serial] Istio with passt binding Virtual Machine with
        istio supported interface Outbound traffic With Sidecar allowing only registered
        external services VMI with no explicit ports Should not be able to reach http
        service outside of mesh'
      status: skipped
    - name: '[sig-storage] [Serial]K8s IO events [test_id:6225]Should catch the IO
        error event'
      status: skipped
    - name: '[sig-compute] vitiofs config volumes With a single ConfigMap volume Should
        be the mounted virtiofs layout the same for a pod and vmi'
      status: skipped
    - name: '[sig-compute] vitiofs config volumes With a single Secret volume Should
        be the mounted virtiofs layout the same for a pod and vmi'
      status: skipped
    - name: '[sig-compute] vitiofs config volumes With a ServiceAccount defined Should
        be the namespace and token the same for a pod and vmi with virtiofs'
      status: skipped
    - name: '[sig-compute] vitiofs config volumes With a DownwardAPI defined Should
        be the namespace and token the same for a pod and vmi with virtiofs'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        scraped metrics [test_id:4135]should find VMI namespace on namespace label
        of the metric'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Start a VirtualMachineInstance when
        the controller pod is not running and an election happens [test_id:4642]should
        elect a new controller pod'
      status: skipped
    - name: '[Serial][sig-compute] virt-handler node restrictions via validatingAdmissionPolicy
        reject not allowed patches to node'
      status: skipped
    - name: '[Serial][sig-compute] virt-handler node restrictions via validatingAdmissionPolicy
        allow kubevirt related patches to node'
      status: skipped
    - name: '[sig-network] Port-forward VMI With masquerade binding when performing
        port-forward from a local port to a VMI''s declared port should reach the
        vmi IPv4'
      status: skipped
    - name: '[sig-network] Port-forward VMI With masquerade binding when performing
        port-forward from a local port to a VMI''s declared port should reach the
        vmi IPv6'
      status: skipped
    - name: '[sig-network] Port-forward VMI With masquerade binding when performing
        port-forward from a local port to a VMI with no declared ports should reach
        the vmi IPv4'
      status: skipped
    - name: '[sig-network] Port-forward VMI With masquerade binding when performing
        port-forward from a local port to a VMI with no declared ports should reach
        the vmi IPv6'
      status: skipped
    - name: '[sig-network] Port-forward VMI With masquerade binding when performing
        port-forward from a local port to a VMI''s non-declared port should not reach
        the vmi IPv4'
      status: skipped
    - name: '[sig-network] Port-forward VMI With masquerade binding when performing
        port-forward from a local port to a VMI''s non-declared port should not reach
        the vmi IPv6'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        when virt-handler is deleted [Serial][test_id:4716]should label the node with
        kubevirt.io/schedulable=false'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [test_id:1619]should success'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [test_id:1620]should start it'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [test_id:6095]should start in paused state if start
        strategy set to paused'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [test_id:1621]should attach virt-launcher to it'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [test_id:3195]should carry annotations to pod'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [test_id:3196]should carry kubernetes and kubevirt
        annotations to pod'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance Should prevent eviction when EvictionStratgy: External'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [test_id:1622]should log libvirtd logs'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance log libvirtd debug logs should be [test_id:3197]enabled
        when debugLogs label defined'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance log libvirtd debug logs should be [test_id:8530]enabled
        when customLogFilters defined'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance log libvirtd debug logs should be [test_id:8531]enabled
        when log verbosity is high'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance log libvirtd debug logs should be [test_id:8532]disabled
        when log verbosity is low'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance log libvirtd debug logs should be [test_id:8533]disabled
        when log verbosity, debug logs and customLogFilters are not defined'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [test_id:1623]should reject POST if validation webhook
        deems the spec invalid'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [test_id:1624]should reject PATCH if schema is invalid'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance when name is longer than 63 characters [test_id:1625]should
        start it'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance when it already exist [test_id:1626]should be rejected'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with boot order [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]should
        be able to boot from selected disk [test_id:1627]Alpine as first boot'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with boot order [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]should
        be able to boot from selected disk [test_id:1628]Cirros as first boot'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with user-data without k8s secret [test_id:1629][posneg:negative]should
        not be able to start virt-launcher pod'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with user-data without k8s secret [test_id:1630]should
        log warning and proceed once the secret is there'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with nodeselector [test_id:5760]should check if vm''s
        with non existing nodeselector is not running and node selector is not updated'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with nodeselector [test_id:5761]should check if vm
        with valid node selector is scheduled and running and node selector is not
        updated'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance when virt-launcher crashes [Serial][test_id:1631]should
        be stopped and have Failed phase'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]when virt-handler crashes [test_id:1632]should
        recover and continue management'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]when virt-handler is responsive [test_id:1633]should
        indicate that a node is ready for vmis'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]when virt-handler is responsive [test_id:3198]device
        plugins should re-register if the kubelet restarts'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]when virt-handler is not responsive [test_id:1634]the
        node controller should mark the node as unschedulable when the virt-handler
        heartbeat has timedout'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with node tainted [test_id:1635]the vmi with
        tolerations should be scheduled'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with node tainted [test_id:1636]the vmi without
        tolerations should not be scheduled'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with affinity [test_id:1637]the vmi with node affinity
        and no conflicts should be scheduled'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with affinity [test_id:1638]the vmi with node affinity
        and anti-pod affinity should not be scheduled'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with default cpu model [test_id:3199]should
        set default cpu model when vmi doesn''t have it set'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with default cpu model [test_id:3200]should
        not set default cpu model when vmi has it set'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with default cpu model [sig-compute][test_id:3201]should
        set cpu model to default when vmi does not have it set and default cpu model
        is not set'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with default cpu model should add node selector
        to virt-launcher when setting default cpuModel in kubevirtCR'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with default cpu model should prefer node
        selector of the vmi if cpuModel field is set in kubevirtCR and in the vmi'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with node feature discovery [test_id:1639]the
        vmi with cpu.model matching a nfd label on a node should be scheduled'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with node feature discovery [test_id:1640]the
        vmi with cpu.model that cannot match an nfd label on node should not be scheduled'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with node feature discovery [test_id:3202]the
        vmi with cpu.features matching nfd labels on a node should be scheduled'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with node feature discovery [test_id:3203]the
        vmi with cpu.features that cannot match nfd labels on a node should not be
        scheduled'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance [Serial]with node feature discovery [test_id:3204]the
        vmi with cpu.feature policy ''forbid'' should not be scheduled on a node with
        that cpu feature label'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with non default namespace [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]should
        log libvirt start and stop lifecycle events of the domain [test_id:1641]Default
        test namespace'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance with non default namespace [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]should
        log libvirt start and stop lifecycle events of the domain [test_id:1642]Alternative
        test namespace'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance VirtualMachineInstance Emulation Mode [test_id:1643]should
        enable emulation in virt-launcher'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance VirtualMachineInstance Emulation Mode [test_id:1644]should
        be reflected in domain XML'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance VirtualMachineInstance Emulation Mode [test_id:1645]should
        request a TUN device but not KVM'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance VM Accelerated Mode [test_id:1646]should request
        a KVM and TUN device'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance VM Accelerated Mode [test_id:1647]should not enable
        emulation in virt-launcher'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Creating
        a VirtualMachineInstance VM Accelerated Mode [test_id:1648]Should provide
        KVM via plugin framework'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Get a VirtualMachineInstance
        when that not exist [test_id:1649]should return 404'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][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''s Pod [test_id:1650]should result in the VirtualMachineInstance
        moving to a finalized state'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][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 an active pod. [test_id:1651]should result in
        pod being terminated'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][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 ACPI and some grace period seconds [rfe_id:273][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        result in vmi status succeeded [test_id:1653]with set grace period seconds'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][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 ACPI and some grace period seconds [rfe_id:273][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        result in vmi status succeeded [test_id:1654]with default grace period seconds'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][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'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [Serial][rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Killed
        VirtualMachineInstance [test_id:1656]should be in Failed phase'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        [Serial][rfe_id:273][crit:high][vendor:cnv-qe@redhat.com][level:component]Killed
        VirtualMachineInstance [test_id:1657]should be left alone by virt-handler'
      status: skipped
    - name: '[rfe_id:273][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIlifecycle
        replicaset with topology spread constraints Replicas should be spread across
        nodes'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        scale [test_id:1405]to three, to two and then to zero replicas'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        scale [test_id:1406]to five, to six and then to zero replicas'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        scale with scale subresource [test_id:1407]to three, to two and then to zero
        replicas'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        scale with scale subresource [test_id:1408]to five, to six and then to zero
        replicas'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        scale with the horizontal pod autoscaler [test_id:1409]to three, to two and
        then to one replicas'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component]should
        scale with the horizontal pod autoscaler [test_id:1410]to five, to six and
        then to one replicas'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [test_id:1411]should be rejected on POST if spec is invalid'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [test_id:1412]should reject POST if validation webhoook deems the spec is
        invalid'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [test_id:1413]should update readyReplicas once VMIs are up'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [test_id:1414]should return the correct data when using server-side printing'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [test_id:1415]should remove VMIs once they are marked for deletion'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [test_id:1416]should remove owner references on the VirtualMachineInstance
        if it is orphan deleted'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [test_id:1417]should not scale when paused and scale when resume'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [test_id:1418] should replace finished VMIs'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        should replace a VMI immediately when a virt-launcher pod gets deleted'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachineInstanceReplicaSet
        [test_id:4121]should create and verify kubectl/oc output for vm replicaset'
      status: skipped
    - name: '[sig-compute]Health Monitoring A VirtualMachineInstance with a watchdog
        device [test_id:4641]should be shut down when the watchdog expires'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring Cluster VM metrics kubevirt_number_of_vms
        should reflect the number of VMs'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VMI metrics should have kubevirt_vmi_phase_transition_time_seconds
        buckets correctly configured'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VMI metrics should have kubevirt_rest_client_requests_total
        for the ''virtualmachineinstances'' resource'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM status metrics Should be available
        for a running VM'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM status metrics Should be available
        for a paused VM'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM status metrics Should not be
        available for a stopped VM'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM migration metrics Should correctly
        update metrics on successful VMIM'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM migration metrics Should correctly
        update metrics on failing VMIM'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM snapshot metrics [test_id:8639]Number
        of disks restored and total restored bytes metric values should be correct'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM snapshot metrics Snapshot succeeded
        timestamp metric values should be correct'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM metrics that are based on the
        guest agent [test_id:11267]should have kubevirt_vmi_info correctly configured
        with guest OS labels'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring Metrics that are based on VMI connections
        should have kubevirt_vmi_last_api_connection_timestamp_seconds correctly configured'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM alerts [QUARANTINE] should fire
        KubevirtVmHighMemoryUsage alert'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM alerts [test_id:9260] should
        fire OrphanedVirtualMachineInstances alert'
      status: skipped
    - name: '[Serial][sig-monitoring]VM Monitoring VM alerts should fire VMCannotBeEvicted
        alert'
      status: skipped
    - name: '[sig-performance]Control Plane Performance Density Testing using kwok
        kwok density tests create a batch of fake VMIs should sucessfully create all
        fake VMIs'
      status: skipped
    - name: '[sig-performance]Control Plane Performance Density Testing using kwok
        kwok density tests create a batch of fake VMs should sucessfully create all
        fake VMs'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Post Copy Live Migration Starting a VirtualMachineInstance  migration postcopy
        with datavolume [test_id:5004] should be migrated successfully, using guest
        agent on VM with postcopy'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Post Copy Live Migration Starting a VirtualMachineInstance  migration postcopy
        should migrate using for postcopy [test_id:4747] using a migration policy'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Post Copy Live Migration Starting a VirtualMachineInstance  migration postcopy
        should migrate using for postcopy [test_id:4747] using [Serial] Kubevirt CR'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        VM Post Copy Live Migration Starting a VirtualMachineInstance  migration postcopy
        should migrate using for postcopy [Serial] and fail should make sure that
        VM restarts after failure'
      status: skipped
    - name: '[sig-network] Primary Pod Network Status VMI connected to the pod network
        using the default (implicit) binding should report PodIP as its own on interface
        status'
      status: skipped
    - name: '[sig-network] Primary Pod Network Status VMI connected to the pod network
        using bridge binding when Guest Agent exists should report PodIP/s on interface
        status'
      status: skipped
    - name: '[sig-network] Primary Pod Network Status VMI connected to the pod network
        using bridge binding when no Guest Agent exists should report PodIP as its
        own on interface status'
      status: skipped
    - name: '[sig-network] Primary Pod Network Status VMI connected to the pod network
        using masquerade binding when Guest Agent exists [test_id:4153]should report
        PodIP/s as its own on interface status'
      status: skipped
    - name: '[sig-network] Primary Pod Network Status VMI connected to the pod network
        using masquerade binding when no Guest Agent exists [Conformance] should report
        PodIP as its own on interface status'
      status: passed
    - name: '[sig-compute-realtime][Serial]Realtime should start the realtime VM when
        no mask is specified'
      status: skipped
    - name: '[sig-compute-realtime][Serial]Realtime should start the realtime VM when
        realtime mask is specified'
      status: skipped
    - name: '[Serial][sig-compute][USB] host USB Passthrough with usb storage with
        emulated USB devices Should successfully passthrough 1 emulated USB device'
      status: skipped
    - name: '[Serial][sig-compute][USB] host USB Passthrough with usb storage with
        emulated USB devices Should successfully passthrough 2 emulated USB devices'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool pool should scale to three, to two and
        then to zero replicas'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool pool should scale to five, to six and
        then to zero replicas'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool should be rejected on POST if spec is
        invalid'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool should reject POST if vmi spec is invalid'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool should remove VMs once they are marked
        for deletion'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool should handle pool with dataVolumeTemplates'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool should replace deleted VM and get replacement'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool should roll out VM template changes without
        impacting VMI'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool should roll out VMI template changes
        and proactively roll out new VMIs'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool should remove owner references on the
        VirtualMachine if it is orphan deleted'
      status: skipped
    - name: '[sig-compute]VirtualMachinePool should not scale when paused and scale
        when resume'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]ContainerDisk
        [rfe_id:273][crit:medium][vendor:cnv-qe@redhat.com][level:component]Starting
        and stopping the same VirtualMachine with ephemeral registry disk [test_id:1463][Conformance]
        should success multiple times'
      status: passed
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]ContainerDisk
        [rfe_id:273][crit:medium][vendor:cnv-qe@redhat.com][level:component]Starting
        a VirtualMachineInstance [Serial]should obey the disk verification limits
        in the KubeVirt CR [test_id:7182]disk verification should fail when the memory
        limit is too low'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]ContainerDisk
        [rfe_id:273][crit:medium][vendor:cnv-qe@redhat.com][level:component]Starting
        from custom image location with disk at /custom-disk/downloaded [test_id:1466]should
        boot normally'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]ContainerDisk
        [rfe_id:273][crit:medium][vendor:cnv-qe@redhat.com][level:component]Starting
        with virtio-win with virtio-win as secondary disk [test_id:1467]should boot
        and have the virtio as sata CDROM'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]ContainerDisk
        [rfe_id:4052][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component]VMI
        disk permissions with ephemeral registry disk [test_id:4299]should not have
        world write permissions'
      status: skipped
    - name: '[rfe_id:588][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]ContainerDisk
        Bogus container disk path that points to outside of the volume should be rejected
        on VMI creation'
      status: skipped
    - name: '[sig-compute][Serial]CPU Hotplug with requests without topology should
        be able to start'
      status: skipped
    - name: '[sig-compute][Serial]CPU Hotplug with Kubevirt CR declaring MaxCpuSockets
        should be able to start'
      status: skipped
    - name: '[sig-compute][Serial]CPU Hotplug A VM with cpu.maxSockets set higher
        than cpu.sockets [test_id:10811]should successfully plug vCPUs'
      status: skipped
    - name: '[sig-compute][Serial]CPU Hotplug A VM with cpu.maxSockets set higher
        than cpu.sockets [test_id:10822]should successfully plug guaranteed vCPUs'
      status: skipped
    - name: '[sig-compute][Serial]CPU Hotplug Abort CPU change should cancel the automated
        workload update'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [Serial]with
        error disk should pause VMI on IO error'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [Serial]with
        error disk should report IO errors in the guest with errorPolicy set to report'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        Alpine PVC should be successfully started [test_id:3130]with Disk PVC'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        Alpine PVC should be successfully started [test_id:3131]with CDRom PVC'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        Alpine PVC should be successfully started [test_id:4618]with NFS Disk PVC
        using ipv4 address of the NFS pod'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        Alpine PVC should be successfully started [Serial]with NFS Disk PVC using
        ipv6 address of the NFS pod'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        Alpine PVC should be successfully started [Serial]with NFS Disk PVC using
        ipv4 address of the NFS pod not owned by qemu'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        Alpine PVC should be successfully started and stopped multiple times [test_id:3132]with
        Disk PVC'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        Alpine PVC should be successfully started and stopped multiple times [test_id:3133]with
        CDRom PVC'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        an emptyDisk defined [test_id:3134]should create a writeable emptyDisk with
        the right capacity'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        an emptyDisk defined and a specified serial number [test_id:3135]should create
        a writeable emptyDisk with the specified serial number'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        ephemeral alpine PVC should be successfully started [test_id:3136]with Ephemeral
        PVC'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        ephemeral alpine PVC should be successfully started [test_id:4619]with Ephemeral
        PVC from NFS using ipv4 address of the NFS pod'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        ephemeral alpine PVC should be successfully started with Ephemeral PVC from
        NFS using ipv6 address of the NFS pod'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        ephemeral alpine PVC [test_id:3137]should not persist data'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        VirtualMachineInstance with two PVCs [test_id:3138]should start vmi multiple
        times'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [Serial]With
        feature gates disabled for [test_id:4620]HostDisk, it should fail to start
        a VMI'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2298][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        With HostDisk and PVC initialization With a HostDisk defined With ''DiskExistsOrCreate''
        type Should create a disk image and start [test_id:851]with virtio driver'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2298][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        With HostDisk and PVC initialization With a HostDisk defined With ''DiskExistsOrCreate''
        type Should create a disk image and start [test_id:3057]with sata driver'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2298][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        With HostDisk and PVC initialization With a HostDisk defined With ''DiskExistsOrCreate''
        type [test_id:3107]should start with multiple hostdisks in the same directory'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2298][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        With HostDisk and PVC initialization With a HostDisk defined With ''DiskExists''
        type [test_id:2306]Should use existing disk image and start'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2298][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        With HostDisk and PVC initialization With a HostDisk defined With ''DiskExists''
        type [test_id:847]Should fail with a capacity option'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2298][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        With HostDisk and PVC initialization With a HostDisk defined With unknown
        hostDisk type [test_id:852]Should fail to start VMI'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2298][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        With HostDisk and PVC initialization With multiple empty PVCs [test_id:868]
        Should initialize an empty PVC by creating a disk.img'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2298][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        With HostDisk and PVC initialization With smaller than requested PVCs [Serial][test_id:3108]Should
        not initialize an empty PVC with a disk.img when disk is too small even with
        toleration'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2298][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        With HostDisk and PVC initialization With smaller than requested PVCs [Serial][test_id:3109]Should
        initialize an empty PVC with a disk.img when disk is too small but within
        toleration'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2288][crit:high][vendor:cnv-qe@redhat.com][level:component][storage-req]
        With Cirros BlockMode PVC [test_id:1015]should be successfully started'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [storage-req][rfe_id:2288][crit:high][vendor:cnv-qe@redhat.com][level:component]With
        Alpine block volume PVC [test_id:3139]should be successfully started'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [rfe_id:2288][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component]
        With not existing PVC [test_id:1040] should get unschedulable condition'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance With both SCSI
        and SATA devices should successfully start with distinct device names'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance With both SCSI
        and SATA devices With a USB device [test_id:9797]should successfully start
        and have the USB storage device attached'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [storage-req]
        With a volumeMode block backed ephemeral disk should generate the pod with
        the volumeDevice'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance disk shareable
        tunable should successfully start 2 VMs with a shareable disk'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance write and read
        data from a shared disk should successfully write and read data'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [Serial]with
        lun disk should run the VMI using PVC source'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [Serial]with
        lun disk should run the VMI using DataVolume source'
      status: skipped
    - name: '[sig-storage] Storage Starting a VirtualMachineInstance [Serial]with
        lun disk should run the VMI created with a DataVolume source and use the LUN
        disk'
      status: skipped
    - name: '[sig-compute][virtctl]SCP should copy a local file back and forth using
        the native scp method'
      status: skipped
    - name: '[sig-compute][virtctl]SCP should copy a local file back and forth using
        the local scp method with --local-ssh flag'
      status: skipped
    - name: '[sig-compute][virtctl]SCP should copy a local file back and forth using
        the local scp method without --local-ssh flag'
      status: skipped
    - name: '[sig-compute][virtctl]SCP should copy a local directory back and forth
        using the native scp method'
      status: skipped
    - name: '[sig-compute][virtctl]SCP should copy a local directory back and forth
        using the local scp method with --local-ssh flag'
      status: skipped
    - name: '[sig-compute][virtctl]SCP should copy a local directory back and forth
        using the local scp method without --local-ssh flag'
      status: skipped
    - name: '[sig-compute][virtctl]SCP local-ssh flag should be unavailable in virtctl'
      status: skipped
    - name: '[sig-compute][Serial]NUMA [test_id:7299] topology should be mapped to
        the guest and hugepages should be allocated'
      status: skipped
    - name: '[Serial][sig-compute]Windows VirtualMachineInstance with winrm connection
        [ref_id:139]VMI is created [test_id:240]should have correct UUID'
      status: skipped
    - name: '[Serial][sig-compute]Windows VirtualMachineInstance with winrm connection
        [ref_id:139]VMI is created [test_id:3159]should have default masquerade IP'
      status: skipped
    - name: '[Serial][sig-compute]Windows VirtualMachineInstance with winrm connection
        [ref_id:139]VMI is created [test_id:3160]should have the domain set properly'
      status: skipped
    - name: '[Serial][sig-compute]Windows VirtualMachineInstance with winrm connection
        VMI with subdomain is created should have the domain set properly with subdomain'
      status: skipped
    - name: '[Serial][sig-compute]Windows VirtualMachineInstance with winrm connection
        with bridge binding should be recognized by other pods in cluster'
      status: skipped
    - name: '[sig-network] bridge nic-hotplug a running VM can be hotplugged a network
        interface In place'
      status: skipped
    - name: '[sig-network] bridge nic-hotplug a running VM can be hotplugged a network
        interface Migration based'
      status: skipped
    - name: '[sig-network] bridge nic-hotplug a running VM can migrate a VMI with
        hotplugged interfaces In place'
      status: skipped
    - name: '[sig-network] bridge nic-hotplug a running VM can migrate a VMI with
        hotplugged interfaces Migration based'
      status: skipped
    - name: '[sig-network] bridge nic-hotplug a running VM has connectivity over the
        secondary network In place'
      status: skipped
    - name: '[sig-network] bridge nic-hotplug a running VM has connectivity over the
        secondary network Migration based'
      status: skipped
    - name: '[sig-network] bridge nic-hotplug a running VM is able to hotplug multiple
        network interfaces In place'
      status: skipped
    - name: '[sig-network] bridge nic-hotplug a running VM is able to hotplug multiple
        network interfaces Migration based'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Live Migration All containers should complete
        in source virt-launcher pod after migration'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface SSH traffic With VMI having explicit ports
        specified should ssh to VMI with Istio proxy'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface SSH traffic With VMI having no explicit ports
        specified should ssh to VMI with Istio proxy'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Inbound traffic With VMI having explicit ports
        specified request to VMI should reach HTTP server on service declared port
        on VMI with explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Inbound traffic With VMI having explicit ports
        specified request to VMI should reach HTTP server on service undeclared port
        on VMI with explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Inbound traffic With VMI having no explicit
        ports specified request to VMI should reach HTTP server on service declared
        port on VMI with no explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Inbound traffic With VMI having no explicit
        ports specified request to VMI should reach HTTP server on service undeclared
        port on VMI with no explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Inbound traffic With VMI having no explicit
        ports specified Should not be able to reach service running on Istio restricted
        port'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Inbound traffic With PeerAuthentication enforcing
        mTLS With VMI having explicit ports specified client outside mesh should NOT
        reach VMI HTTP server on service declared port on VMI with explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Inbound traffic With PeerAuthentication enforcing
        mTLS With VMI having explicit ports specified client outside mesh should NOT
        reach VMI HTTP server on service undeclared port on VMI with explicit ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Inbound traffic With PeerAuthentication enforcing
        mTLS With VMI having no explicit ports specified client outside mesh should
        NOT reach VMI HTTP server on service declared port on VMI with no explicit
        ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Inbound traffic With PeerAuthentication enforcing
        mTLS With VMI having no explicit ports specified client outside mesh should
        NOT reach VMI HTTP server on service undeclared port on VMI with no explicit
        ports'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Outbound traffic VMI with explicit ports Should
        be able to reach http server outside of mesh'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Outbound traffic VMI with no explicit ports
        Should be able to reach http server outside of mesh'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Outbound traffic With Sidecar allowing only
        registered external services VMI with explicit ports Should not be able to
        reach http service outside of mesh'
      status: skipped
    - name: '[sig-network] [Serial] Istio with masquerade binding Virtual Machine
        with istio supported interface Outbound traffic With Sidecar allowing only
        registered external services VMI with no explicit ports Should not be able
        to reach http service outside of mesh'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure cluster profiler for pprof data aggregation
        when ClusterProfiler feature gate is disabled it should prevent subresource
        access'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure cluster profiler for pprof data aggregation
        when ClusterProfiler feature gate is enabled it should allow subresource access'
      status: skipped
    - name: '[sig-network] VirtualMachineInstance with macvtap network binding plugin
        two VMs with macvtap interface should be able to communicate over macvtap
        network'
      status: skipped
    - name: '[sig-network] VirtualMachineInstance with macvtap network binding plugin
        VMI migration should be successful when the VMI MAC address is defined in
        its spec'
      status: skipped
    - name: '[sig-network] VirtualMachineInstance with macvtap network binding plugin
        VMI migration with live traffic should keep connectivity after a migration'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [test_id:3812]explain vm/vmi [test_id:3810]explain
        vm'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [test_id:3812]explain vm/vmi [test_id:3811]explain
        vmi'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [test_id:3812]explain vm/vmi [test_id:5178]explain
        vmim'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [test_id:3812]explain vm/vmi [test_id:5179]explain
        kv'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [test_id:3812]explain vm/vmi [test_id:5180]explain
        vmsnapshot'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [test_id:3812]explain vm/vmi [test_id:5181]explain
        vmsnapshotcontent'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [test_id:5182]vmipreset have validation'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [test_id:5183]vmirs have validation'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [rfe_id:3423][vendor:cnv-qe@redhat.com][level:component]oc/kubectl
        get vm/vmi tests should verify set of columns for [test_id:3464]virtualmachine'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [rfe_id:3423][vendor:cnv-qe@redhat.com][level:component]oc/kubectl
        get vm/vmi tests should verify set of columns for [test_id:3465]virtualmachineinstance'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [rfe_id:3423][vendor:cnv-qe@redhat.com][level:component]oc/kubectl
        get vm/vmi tests should verify set of wide columns for [test_id:3468]virtualmachine'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration [rfe_id:3423][vendor:cnv-qe@redhat.com][level:component]oc/kubectl
        get vm/vmi tests should verify set of wide columns for [test_id:3466]virtualmachineinstance'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration VM instance migration ''kubectl get
        vmim'' print the expected columns and their corresponding values'
      status: skipped
    - name: '[sig-compute]oc/kubectl integration oc/kubectl logs oc/kubectl logs <vmi-pod>
        return default container log'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute][serial]
        InstancetypeReferencePolicy should result in running VirtualMachine when set
        to reference'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute][serial]
        InstancetypeReferencePolicy should result in running VirtualMachine when set
        to expand'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute][serial]
        InstancetypeReferencePolicy should result in running VirtualMachine when set
        to expandAll'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Node-labeller basic labelling skip
        node reconciliation when node has skip annotation'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Node-labeller basic labelling [test_id:6246]
        label nodes with cpu model, cpu features and host cpu model'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Node-labeller basic labelling [test_id:6247]
        should set default obsolete cpu models filter when obsolete-cpus-models is
        not set in kubevirt config'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Node-labeller basic labelling [test_id:6995]should
        expose tsc frequency and tsc scalability'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Node-labeller advanced labelling
        [test_id:6249] should update node with new cpu model label set'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Node-labeller advanced labelling
        [test_id:6250] should update node with new cpu model vendor label'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Node-labeller advanced labelling
        [test_id:6252] should remove all cpu model labels (all cpu model are in obsolete
        list)'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Node-labeller [Serial]node with obsolete
        host-model cpuModel [Serial]should not schedule vmi with host-model cpuModel
        to node with obsolete host-model cpuModel'
      status: skipped
    - name: '[Serial][Sysprep][sig-compute]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'
      status: skipped
    - name: '[sig-monitoring]Metrics Prometheus metrics should contain virt components
        metrics'
      status: skipped
    - name: '[sig-compute]CloudInitHookSidecars VMI definition with CloudInit hook
        sidecar [test_id:3167]should successfully start with hook sidecar annotation'
      status: skipped
    - name: '[sig-compute]CloudInitHookSidecars VMI definition with CloudInit hook
        sidecar [test_id:3168]should call Collect and PreCloudInitIso on the hook
        sidecar'
      status: skipped
    - name: '[sig-compute]CloudInitHookSidecars VMI definition with CloudInit hook
        sidecar [test_id:3169]should have cloud-init user-data from sidecar'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to single SRIOV network should have cloud-init
        meta_data with aligned cpus to sriov interface numa node for VMIs with dedicatedCPUs'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to single SRIOV network should have cloud-init
        meta_data with tagged sriov nics'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to single SRIOV network [test_id:1754]should
        create a virtual machine with sriov interface'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to single SRIOV network [test_id:1754]should
        create a virtual machine with sriov interface with all pci devices on the
        root bus'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to single SRIOV network [test_id:3959]should
        create a virtual machine with sriov interface and dedicatedCPUs'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to single SRIOV network [test_id:3985]should
        create a virtual machine with sriov interface with custom MAC address'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to single SRIOV network migration should
        be successful with a running VMI on the target'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to two SRIOV networks [test_id:1755]should
        create a virtual machine with two sriov interfaces referring the same resource'
      status: skipped
    - name: '[Serial]SRIOV Connected to multiple SRIOV networks should correctly plug
        all the interfaces based on the specified MAC and (guest) PCI addresses'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to link-enabled SRIOV network [test_id:3956]should
        connect to another machine with sriov interface over IP'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to link-enabled SRIOV network With VLAN should
        be able to ping between two VMIs with the same VLAN over SRIOV network'
      status: skipped
    - name: '[Serial]SRIOV VMI connected to link-enabled SRIOV network With VLAN should
        NOT be able to ping between Vlaned VMI and a non Vlaned VMI'
      status: skipped
    - name: Ensure stable functionality by repeately starting vmis many times without
        issues
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure Node Restriction Should disallow
        to modify VMs on different node'
      status: skipped
    - name: '[sig-compute] virt-api scaling virt-api replicas should be scaled as
        expected'
      status: skipped
    - name: '[sig-compute] virt-api scaling [Serial]virt-api replicas should be determined
        by patch if exist'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:4126][crit:medium][vendor:cnv-qe@redhat.com][level:component]Taints
        and toleration CriticalAddonsOnly taint set on a node [test_id:4134] kubevirt
        components on that node should not evict'
      status: skipped
    - name: '[rfe_id:609][sig-compute]VMIheadless [rfe_id:609]Creating a VirtualMachineInstance
        with headless [test_id:709][posneg:positive]should connect to console'
      status: skipped
    - name: '[Serial][sig-compute]HostDevices with ephemeral disk with emulated PCI
        devices Should successfully passthrough an emulated PCI device'
      status: skipped
    - name: '[Serial][sig-compute]HostDevices with ephemeral disk with emulated PCI
        devices Should successfully passthrough 2 emulated PCI devices'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with existing PVC Should be able
        to get and remove memory dump [test_id:8499]calling endpoint directly'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with existing PVC Should be able
        to get and remove memory dump [test_id:8500]using virtctl'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with existing PVC [test_id:8502]Run
        multiple memory dumps'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with existing PVC [test_id:8503]Run
        memory dump to a pvc, remove and run memory dump to different pvc'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with existing PVC [test_id:8506]Run
        memory dump, stop vm and remove memory dump'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with existing PVC [test_id:8515]Run
        memory dump, stop vm start vm'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with existing PVC [test_id:8501]Run
        memory dump with pvc too small should fail'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with creating a PVC [test_id:9034]Should
        be able to get and remove memory dump'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with creating a PVC [test_id:9035]Run
        multiple memory dumps'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with creating a PVC [test_id:9036]Run
        memory dump to creates a pvc, remove and run memory dump to create a different
        pvc'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with creating a PVC [test_id:9341]Should
        be able to remove memory dump while memory dump is stuck'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with download [test_id:9344]should
        create memory dump and download it'
      status: skipped
    - name: '[sig-storage] Memory dump Memory dump with download [test_id:9343]should
        download existing memory dump'
      status: skipped
    - name: '[sig-network] Slirp VMI with SLIRP interface, custom mac and port is
        configured correctly'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests With simple VM [test_id:4609]should
        successfully create a snapshot'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests With simple VM [test_id:4610]create
        a snapshot when VM is running should succeed'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests With simple VM should create
        a snapshot when VM runStrategy is Manual'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests With simple VM VM should contain
        snapshot status for all volumes'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot [test_id:6767]with volumes and guest agent available'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot [test_id:6768]with volumes and no guest agent available'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot [test_id:6769]without volumes with guest agent available'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot [test_id:6837]delete snapshot after freeze, expect vm unfreeze'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot [test_id:6949]should unfreeze vm if snapshot fails when deadline
        exceeded'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot [test_id:7472]should succeed online snapshot with hot plug disk'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot should report appropriate event when freeze fails'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot Calling Velero hooks should freeze/unfreeze VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot [test_id:9647]Calling Velero hooks should not error if no guest
        agent'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot Calling Velero hooks should error if VM is Paused'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With online
        vm snapshot with memory dump [test_id:8922]should include memory dump in vm
        snapshot'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With more complicated
        VM should successfully recreate status'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With more complicated
        VM VM should contain snapshot status for all volumes'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With more complicated
        VM should error if VolumeSnapshot deleted'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With more complicated
        VM should not error if VolumeSnapshot has error'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With more complicated
        VM [test_id:6952]snapshot change phase to in progress and succeeded and then
        should not fail'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With more complicated
        VM [test_id:6838]snapshot should fail when deadline exceeded due to volume
        snapshots failure'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] vmsnapshot should
        update error if vmsnapshotcontent is unready to use and error'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] [Serial]With
        more complicated VM with/out GC of succeeded DV should successfully create
        a snapshot [test_id:4611] without DV garbage collection'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] [Serial]With
        more complicated VM with/out GC of succeeded DV should successfully create
        a snapshot [test_id:8668] with DV garbage collection'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] with independent
        DataVolume should accurately report DataVolume provisioning with DataVolume
        volume'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] with independent
        DataVolume should accurately report DataVolume provisioning with PVC volume'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] with independent
        DataVolume [test_id:9705]Should show included and excluded volumes in the
        snapshot'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With VM using
        instancetype and preferences Bug #8435 - should create a snapshot successfully
        with running source VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineSnapshot Tests [storage-req] With VM using
        instancetype and preferences Bug #8435 - should create a snapshot successfully
        with stopped source VM'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure virt-handler should enable/disable
        ksm and add/remove annotation on all the nodes when the selector is empty'
      status: skipped
    - name: '[sig-compute][virtctl]SSH should succeed to execute a command on the
        VM using the native ssh method'
      status: skipped
    - name: '[sig-compute][virtctl]SSH should succeed to execute a command on the
        VM using the local ssh method with --local-ssh flag'
      status: skipped
    - name: '[sig-compute][virtctl]SSH should succeed to execute a command on the
        VM using the local ssh method without --local-ssh flag'
      status: skipped
    - name: '[sig-compute][virtctl]SSH local-ssh flag should be unavailable in virtctl'
      status: skipped
    - name: '[sig-storage] [rfe_id:6364]Guestfs Run libguestfs on PVCs Should successfully
        run libguestfs-test-tool'
      status: skipped
    - name: '[sig-storage] [rfe_id:6364]Guestfs Run libguestfs on PVCs [posneg:positive][test_id:6480]Should
        successfully run guestfs command on a filesystem-based PVC'
      status: skipped
    - name: '[sig-storage] [rfe_id:6364]Guestfs Run libguestfs on PVCs [posneg:negative][test_id:6480]Should
        fail to run the guestfs command on a PVC in use'
      status: skipped
    - name: '[sig-storage] [rfe_id:6364]Guestfs Run libguestfs on PVCs [posneg:positive][test_id:6479]Should
        successfully run guestfs command on a block-based PVC'
      status: skipped
    - name: '[sig-storage] [rfe_id:6364]Guestfs Run libguestfs on PVCs Should successfully
        run guestfs command on a filesystem-based PVC setting the uid'
      status: skipped
    - name: '[sig-storage] [rfe_id:6364]Guestfs Run libguestfs on PVCs with root Should
        successfully run guestfs command on a filesystem-based PVC with root'
      status: skipped
    - name: '[Serial][sig-operator]virt-handler canary upgrade should successfully
        upgrade virt-handler'
      status: skipped
    - name: '[sig-compute]VM Tolerations Updating VMs tolerations should successfully
        live update tolerations'
      status: skipped
    - name: '[sig-compute]VSOCK VM creation should expose a VSOCK device Use virtio
        transitional'
      status: skipped
    - name: '[sig-compute]VSOCK VM creation should expose a VSOCK device Use virtio
        non-transitional'
      status: skipped
    - name: '[sig-compute]VSOCK Live migration should retain the CID for migration
        target'
      status: skipped
    - name: '[sig-compute]VSOCK communicating with VMI via VSOCK should succeed with
        TLS on both sides'
      status: skipped
    - name: '[sig-compute]VSOCK communicating with VMI via VSOCK should succeed without
        TLS on both sides'
      status: skipped
    - name: '[sig-compute]VSOCK should return err if the port is invalid'
      status: skipped
    - name: '[sig-compute]VSOCK should return err if no app listerns on the port'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        USB Redirection [crit:medium][vendor:cnv-qe@redhat.com][level:component] A
        VirtualMachineInstance without usbredir support should fail to connect to
        VMI''s usbredir socket'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        USB Redirection [crit:medium][vendor:cnv-qe@redhat.com][level:component][QUARANTINE]
        A VirtualMachineInstance with usbredir support Should fail when limit is reached'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        USB Redirection [crit:medium][vendor:cnv-qe@redhat.com][level:component][QUARANTINE]
        A VirtualMachineInstance with usbredir support Should work in parallel'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        USB Redirection [crit:medium][vendor:cnv-qe@redhat.com][level:component][QUARANTINE]
        A VirtualMachineInstance with usbredir support Should work several times'
      status: skipped
    - name: '[sig-compute]Controller devices with ephemeral disk a scsi controller
        should appear if enabled'
      status: skipped
    - name: '[sig-compute]Controller devices with ephemeral disk a scsi controller
        should NOT appear if disabled'
      status: skipped
    - name: '[Serial][sig-compute]SwapTest Migration to/from memory overcommitted
        nodes Postcopy Migration of vmi that is dirtying(stress-ng) more memory than
        the source node''s memory'
      status: skipped
    - name: '[Serial][sig-compute]SwapTest Migration to/from memory overcommitted
        nodes Migration of vmi to memory overcommited node'
      status: skipped
    - name: '[Serial][sig-compute]VM Rollout Strategy When using the Stage rollout
        strategy [test_id:11207]should set RestartRequired when changing any spec
        field'
      status: skipped
    - name: '[sig-network] bridge nic-hotunplug a running VM hot-unplug network interface
        succeed In place'
      status: skipped
    - name: '[sig-network] bridge nic-hotunplug a running VM hot-unplug network interface
        succeed Migration based'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:4102][crit:medium][vendor:cnv-qe@redhat.com][level:component]certificates
        [test_id:4099] should be rotated when a new CA is created'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:4102][crit:medium][vendor:cnv-qe@redhat.com][level:component]certificates
        [sig-compute][test_id:4100] should be valid during the whole rotation process'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:4102][crit:medium][vendor:cnv-qe@redhat.com][level:component]certificates
        should be rotated when deleted for  [test_id:4101] virt-operator'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:4102][crit:medium][vendor:cnv-qe@redhat.com][level:component]certificates
        should be rotated when deleted for  [test_id:4103] virt-api'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:4102][crit:medium][vendor:cnv-qe@redhat.com][level:component]certificates
        should be rotated when deleted for  [test_id:4104] virt-controller'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:4102][crit:medium][vendor:cnv-qe@redhat.com][level:component]certificates
        should be rotated when deleted for  [test_id:4105] virt-handlers client side'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:4102][crit:medium][vendor:cnv-qe@redhat.com][level:component]certificates
        should be rotated when deleted for  [test_id:4106] virt-handlers server side'
      status: skipped
    - name: '[sig-compute]Version Check that version parameters where loaded by ldflags
        in build time [test_id:555]Should return a good version information struct'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM and no snapshot
        [test_id:5255]should reject restore'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM with run strategy
        and snapshot should successfully restore'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM and good snapshot
        exists [test_id:5256]should successfully restore'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM and good snapshot
        exists [test_id:5257]should reject restore if VM running'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM and good snapshot
        exists [test_id:5258]should reject restore if another in progress'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM and good snapshot
        exists should fail restoring to a different VM that already exists'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM and good snapshot
        exists restore to a new VM that does not exist with changed name and MAC address'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM with instancetype
        and preferences should use existing ControllerRevisions for an existing VM
        restore with a running VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM with instancetype
        and preferences should use existing ControllerRevisions for an existing VM
        restore with a stopped VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM with instancetype
        and preferences should create new ControllerRevisions for newly restored VM
        with a running VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests With simple VM with instancetype
        and preferences should create new ControllerRevisions for newly restored VM
        with a stopped VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM [test_id:5259]should restore a vm multiple from the same snapshot'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm with restore size bigger then PVC size to the same
        VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm with restore size bigger then PVC size to a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM [QUARANTINE] should restore a vm that boots from a datavolumetemplate [test_id:5260]
        to the same VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM [QUARANTINE] should restore a vm that boots from a datavolumetemplate to
        a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm that boots from a datavolume (not template) [test_id:5261]
        to the same VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm that boots from a datavolume (not template) to a new
        VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm that boots from a PVC [test_id:5262] to the same VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm that boots from a PVC to a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm with containerdisk and blank datavolume [test_id:5263]
        to the same VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm with containerdisk and blank datavolume to a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should reject vm start if restore in progress and allow it to start after
        completion'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should reject vm start if restore in progress and allow it to start after
        vmrestore deletion'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm from an online snapshot [test_id:6053] to the same
        VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm from an online snapshot to a new VM'
      status: skipped
    - name: '[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'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore a vm from an online snapshot with guest agent to a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM [QUARANTINE] should restore an online vm snapshot that boots from a datavolumetemplate
        with guest agent [test_id:6836] to the same VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM [QUARANTINE] should restore an online vm snapshot that boots from a datavolumetemplate
        with guest agent to a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore vm spec at startup without new changes'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore an already cloned virtual machine'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore vm with hot plug disks [test_id:7425] to the same VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM should restore vm with hot plug disks to a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with memory dump should not restore memory dump volume [test_id:8923]to
        the same VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with memory dump should not restore memory dump volume [test_id:8924]to
        a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolumetemplate to the same VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolumetemplate to a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolumetemplate to the same VM, no source pvc'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolumetemplate to a new VM, no source pvc'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolumetemplate to the same VM, no source namespace'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolumetemplate to a new VM, no source namespace'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolume (not template) to the same VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolume (not template) to a new VM'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolume (not template) to the same VM, no source pvc'
      status: skipped
    - name: '[sig-storage] VirtualMachineRestore Tests [storage-req] With a more complicated
        VM with cross namespace clone ability should restore a vm that boots from
        a network cloned datavolume (not template) to a new VM, no source pvc'
      status: skipped
    - name: '[sig-network] Infosource [Serial] VMI with 3 interfaces should have the
        expected entries in vmi status'
      status: skipped
    - name: '[sig-compute] [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]Console
        [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with a serial console [test_id:1588]should return
        OS login'
      status: skipped
    - name: '[sig-compute] [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]Console
        [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with a serial console [test_id:1590]should be able
        to reconnect to console multiple times'
      status: skipped
    - name: '[sig-compute] [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]Console
        [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with a serial console [test_id:1591]should close
        console connection when new console connection is opened'
      status: skipped
    - name: '[sig-compute] [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]Console
        [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with a serial console [test_id:1592]should wait
        until the virtual machine is in running state and return a stream interface'
      status: skipped
    - name: '[sig-compute] [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]Console
        [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with a serial console [test_id:1593]should not
        be connected if scheduled to non-existing host'
      status: skipped
    - name: '[sig-compute] [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]Console
        [rfe_id:127][posneg:negative][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance without a serial console [test_id:4118]should run
        but not be connectable via the serial console'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure downwardMetrics should start a vmi
        and get the metrics [test_id:6535]using a disk'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure downwardMetrics should start a vmi
        and get the metrics using a virtio serial device'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure downwardMetrics metric ResourceProcessorLimit
        should be present'
      status: skipped
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and connectivity between VMI/s is blocked
        by Default-deny networkpolicy [test_id:1511] should fail to reach serverVMI
        from clientVMI'
      status: skipped
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and connectivity between VMI/s is blocked
        by Default-deny networkpolicy [test_id:1512] should fail to reach clientVMI
        from serverVMI'
      status: skipped
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and connectivity between VMI/s is blocked
        by Default-deny networkpolicy [test_id:369] should deny http traffic for ports
        80/81 from clientVMI to serverVMI'
      status: skipped
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and vms limited by allow same namespace networkpolicy
        when client vmi is on default namespace [Conformance][test_id:1513] should
        succeed pinging between two VMI/s in the same namespace'
      status: passed
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and vms limited by allow same namespace networkpolicy
        when client vmi is on alternative namespace [Conformance][test_id:1514] should
        fail pinging between two VMI/s each on different namespaces'
      status: passed
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and ingress traffic to VMI identified via
        label at networkprofile''s labelSelector is blocked when client vmi is on
        alternative namespace [test_id:1515] should fail to reach serverVMI from clientVMIAlternativeNamespace'
      status: skipped
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and ingress traffic to VMI identified via
        label at networkprofile''s labelSelector is blocked when client vmi is on
        default namespace [test_id:1515] should fail to reach serverVMI from clientVMI'
      status: skipped
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and ingress traffic to VMI identified via
        label at networkprofile''s labelSelector is blocked when client vmi is on
        default namespace when another client vmi is on an alternative namespace [test_id:1517]
        should success to reach clientVMI from clientVMIAlternativeNamespace'
      status: skipped
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and TCP connectivity on ports 80 and 81 between
        VMI/s is allowed by networkpolicy [test_id:2774] should allow http traffic
        for ports 80 and 81 from clientVMI to serverVMI'
      status: skipped
    - name: '[sig-network] [rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy
        when three alpine VMs with default networking are started and serverVMI start
        an HTTP server on port 80 and 81 and TCP connectivity on ports 80 between
        VMI/s is allowed by networkpolicy [test_id:2775] should allow http traffic
        at port 80 and deny at port 81 from clientVMI to serverVMI'
      status: skipped
    - name: '[sig-compute]PortForward should successfully open connection to guest'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with RAW kubevirt
        content type'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with RAW gzipped
        kubevirt content type'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with archive
        content type'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with archive
        tarred gzipped content type'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with RAW kubevirt
        content type block'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with RAW kubevirt
        content type PROXY'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with RAW gzipped
        kubevirt content type PROXY'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with archive
        content type PROXY'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with archive
        tarred gzipped content type PROXY'
      status: skipped
    - name: '[sig-storage] Export should make a PVC export available with RAW kubevirt
        content type block PROXY'
      status: skipped
    - name: '[sig-storage] Export Should recreate the exporter pod and secret if the
        pod fails'
      status: skipped
    - name: '[sig-storage] Export Should recreate the exporter pod if the pod is deleted'
      status: skipped
    - name: '[sig-storage] Export Should recreate the service if the service is deleted'
      status: skipped
    - name: '[sig-storage] Export Should handle no pvc existing when export created,
        then creating and populating the pvc'
      status: skipped
    - name: '[sig-storage] Export should be possibe to observe exportserver pod exiting'
      status: skipped
    - name: '[sig-storage] Export Should handle populating an export without a previously
        defined tokenSecretRef'
      status: skipped
    - name: '[sig-storage] Export Should honor TTL by cleaning up the the VMExport
        altogether'
      status: skipped
    - name: '[sig-storage] Export [Serial]Ingress should populate external links and
        cert and contain ingress host'
      status: skipped
    - name: '[sig-storage] Export Route should populate external links and cert and
        contain route host'
      status: skipped
    - name: '[sig-storage] Export should create export from VMSnapshot'
      status: skipped
    - name: '[sig-storage] Export should create export from VMSnapshot with multiple
        volumes'
      status: skipped
    - name: '[sig-storage] Export should mark the status phase skipped on VMSnapshot
        without volumes'
      status: skipped
    - name: '[sig-storage] Export should report export pending if VM is running, and
        start the VM export if the VM is not running, then stop again once VM started'
      status: skipped
    - name: '[sig-storage] Export with limit range [Serial] should report export pending
        if PVC is in use because of VMI using it, and start the VM export if the PVC
        is not in use, then stop again once pvc in use again'
      status: skipped
    - name: '[sig-storage] Export [QUARANTINE] should generate updated DataVolumeTemplates
        on http endpoint when exporting'
      status: skipped
    - name: '[sig-storage] Export [QUARANTINE] should generate updated DataVolumeTemplates
        on http endpoint when exporting snapshot'
      status: skipped
    - name: '[sig-storage] Export [QUARANTINE] Should generate DVs and expanded VM
        definition on http endpoint with multiple volumes'
      status: skipped
    - name: '[sig-storage] Export should mark the status phase skipped on VM without
        volumes'
      status: skipped
    - name: '[sig-storage] Export [Serial] with potential KubeVirt CR update should
        recreate exportserver pod when KubeVirt cert params updated'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Create succeeds using PVC
        source'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Create succeeds using Snapshot
        source'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Create succeeds using VM
        source'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Create fails when the vmexport
        already exists'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Delete succeeds'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Delete succeeds when vmexport
        doesn''t exist'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Create with TTL'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Download a volume with
        vmexport Download succeeds creating and downloading a vmexport using PVC source'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Download a volume with
        vmexport Download succeeds creating and downloading a vmexport using Snapshot
        source'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Download a volume with
        vmexport Download succeeds creating and downloading a vmexport using VM source'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Download a volume with
        vmexport Download succeeds with an already existing vmexport'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Download a volume with
        vmexport Download succeeds with a vmexport without user-defined TokenSecretRef'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Download a volume with
        vmexport Download retains the vmexport resource when it''s been created in
        advance'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Download a volume with
        vmexport Download deletes the vmexport resource when explicitely specified'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Get export manifest from
        vmexport manifest should be successfully retrieved on running VM export without
        --include-secret'
      status: skipped
    - name: '[sig-storage] Export virtctl vmexport command Get export manifest from
        vmexport manifest should be successfully retrieved on running VM export with
        --include-secret'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Up metrics VirtOperatorDown
        and NoReadyVirtOperator should be triggered when virt-operator is down'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Up metrics LowVirtOperatorCount
        should be triggered when virt-operator count is low'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Up metrics VirtControllerDown
        and NoReadyVirtController should be triggered when virt-controller is down'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Up metrics LowVirtControllersCount
        should be triggered when virt-controller count is low'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Up metrics VirtApiDown should
        be triggered when virt-api is down'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Up metrics LowVirtAPICount
        should be triggered when virt-api count is low'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Errors metrics VirtApiRESTErrorsBurst
        and VirtApiRESTErrorsHigh should be triggered when requests to virt-api are
        failing'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Errors metrics VirtOperatorRESTErrorsBurst
        and VirtOperatorRESTErrorsHigh should be triggered when requests to virt-operator
        are failing'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Errors metrics VirtControllerRESTErrorsBurst
        and VirtControllerRESTErrorsHigh should be triggered when requests to virt-controller
        are failing'
      status: skipped
    - name: '[Serial][sig-monitoring]Component Monitoring Errors metrics VirtHandlerRESTErrorsBurst
        and VirtHandlerRESTErrorsHigh should be triggered when requests to virt-handler
        are failing'
      status: skipped
    - name: '[Serial][sig-operator]Operator [test_id:1746]should have created and
        available condition'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial]should reconcile components checking
        updating resource is reverted to original state for  [test_id:6254] deployments'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial]should reconcile components checking
        updating resource is reverted to original state for  [test_id:6255] customresourcedefinitions'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial]should reconcile components checking
        updating resource is reverted to original state for  [test_id:6256] poddisruptionbudgets'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial]should reconcile components checking
        updating resource is reverted to original state for  [test_id:6308] daemonsets'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial]should reconcile components [test_id:6309]
        checking updating service is reverted to original state'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]should
        start a VM [test_id:3144]using virt-launcher with a shasum'
      status: skipped
    - name: '[Serial][sig-operator]Operator [test_id:6987]should apply component configuration
        test VirtualMachineInstancesPerNode'
      status: skipped
    - name: '[Serial][sig-operator]Operator [test_id:4744][Serial]should apply component
        customization test applying and removing a patch'
      status: skipped
    - name: '[Serial][sig-operator]Operator imagePullSecrets should not be present
        if not specified on the KubeVirt CR'
      status: skipped
    - name: '[Serial][sig-operator]Operator imagePullSecrets should be propagated
        if applied on the KubeVirt CR'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]should
        update kubevirt [release-blocker][test_id:3145]from previous release to target
        tested release by patching KubeVirt CR'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]should
        update kubevirt [release-blocker][test_id:3145]from previous release to target
        tested release by updating virt-operator'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [test_id:3146]should be able to delete and re-create kubevirt install'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [rfe_id:3578][crit:high][vendor:cnv-qe@redhat.com][level:component]
        deleting with BlockUninstallIfWorkloadsExist [test_id:3683]should be blocked
        if a workload exists'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [test_id:3148]should be able to create kubevirt install with custom
        image tag'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [test_id:3149]should be able to create kubevirt install with image
        prefix'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [test_id:3150]should be able to update kubevirt install with custom
        image tag'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [test_id:3151]should be able to update kubevirt install when operator
        updates if no custom image tag is set'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [test_id:3152]should fail if KV object already exists'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [test_id:4612]should create non-namespaces resources without owner
        references'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [test_id:4613]should remove owner references on non-namespaces
        resources when updating a resource'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [test_id:5010]should be able to update product related labels of
        kubevirt install'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2291][crit:high][vendor:cnv-qe@redhat.com][level:component]infrastructure
        management [rfe_id:2897][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        OpenShift cluster [test_id:2910]Should have kubevirt SCCs created'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2897][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        ServiceMonitor Disabled [test_id:3154]Should not create RBAC Role or RoleBinding
        for ServiceMonitor'
      status: skipped
    - name: '[Serial][sig-operator]Operator With PrometheusRule Enabled [test_id:4614]Checks
        if the kubevirt PrometheusRule cr exists and verify it''s spec'
      status: skipped
    - name: '[Serial][sig-operator]Operator With PrometheusRule Disabled [test_id:4615]Checks
        that we do not deploy a PrometheusRule cr when not needed'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2937][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        ServiceMonitor Enabled [test_id:2936]Should allow Prometheus to scrape KubeVirt
        endpoints'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:2937][crit:medium][vendor:cnv-qe@redhat.com][level:component]With
        ServiceMonitor Enabled [test_id:4616]Should patch our namespace labels with
        openshift.io/cluster-monitoring=true'
      status: skipped
    - name: '[Serial][sig-operator]Operator [test_id:4617]should adopt previously
        unmanaged entities by updating its metadata'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:4356]Node Placement [test_id:4927]should
        dynamically update infra config'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:4356]Node Placement [test_id:4928]should
        dynamically update workloads config'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:4356]Node Placement should reject
        infra placement configuration with incorrect toleration operator'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:4356]Node Placement should reject
        workload placement configuration with incorrect toleraion operator'
      status: skipped
    - name: '[Serial][sig-operator]Operator [rfe_id:4356]Node Placement [test_id:8235]should
        check if kubevirt components have linux node selector'
      status: skipped
    - name: '[Serial][sig-operator]Operator Replicas should fail to set replicas to
        0'
      status: skipped
    - name: '[Serial][sig-operator]Operator Replicas should dynamically adjust virt-
        pod count and PDBs'
      status: skipped
    - name: '[Serial][sig-operator]Operator Replicas should update new single-replica
        CRs with a finalizer and be stable'
      status: skipped
    - name: '[Serial][sig-operator]Operator Certificate Rotation [test_id:6257]should
        accept valid cert rotation parameters'
      status: skipped
    - name: '[Serial][sig-operator]Operator Certificate Rotation [test_id:6258]should
        reject combining deprecated and new cert rotation parameters'
      status: skipped
    - name: '[Serial][sig-operator]Operator Certificate Rotation [test_id:6259]should
        reject CA expires before rotation'
      status: skipped
    - name: '[Serial][sig-operator]Operator Certificate Rotation [test_id:6260]should
        reject Cert expires before rotation'
      status: skipped
    - name: '[Serial][sig-operator]Operator Certificate Rotation [test_id:6261]should
        reject Cert rotates after CA expires'
      status: skipped
    - name: '[Serial][sig-operator]Operator with VMExport feature gate toggled should
        delete and recreate virt-exportproxy'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial] Seccomp configuration Kubevirt
        profile should install Kubevirt policy'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial] Seccomp configuration Kubevirt
        profile should not install Kubevirt policy'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial] Seccomp configuration VirtualMachineInstance
        Profile with VirtualMachineInstance Profile set to default should not set
        profile'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial] Seccomp configuration VirtualMachineInstance
        Profile with VirtualMachineInstance Profile set to custom should use localhost'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial] Deployment of common-instancetypes
        Should deploy common-instancetypes according to KubeVirt configurable'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial] Deployment of common-instancetypes
        Should take ownership of instancetypes and preferences'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial] Deployment of common-instancetypes
        Should delete resources not in install strategy with instancetypes and preferences'
      status: skipped
    - name: '[Serial][sig-operator]Operator [Serial] Deployment of common-instancetypes
        Should revert changes to instancetypes and preferences'
      status: skipped
    - name: '[sig-network] [Serial]network binding plugin with CNI and Sidecar can
        be used by a VMI as its primary network'
      status: skipped
    - name: '[sig-network] [Serial]network binding plugin with domain attachment tap
        type can run a virtual machine with one macvtap interface'
      status: skipped
    - name: '[sig-network] [Serial]network binding plugin with domain attachment managedTap
        type can run a virtual machine with one primary managed-tap interface'
      status: skipped
    - name: '[sig-network] [Serial]network binding plugin with domain attachment managedTap
        type can establish communication between two VMs'
      status: skipped
    - name: '[sig-compute][virtctl]create vm [test_id:9840]VM with random name and
        default settings'
      status: skipped
    - name: '[sig-compute][virtctl]create vm Example with volume-import flag and PVC
        type'
      status: skipped
    - name: '[sig-compute][virtctl]create vm Example with volume-import flag and Registry
        type'
      status: skipped
    - name: '[sig-compute][virtctl]create vm Example with volume-import flag and Blank
        type'
      status: skipped
    - name: '[sig-compute][virtctl]create vm [test_id:9841]Complex example'
      status: skipped
    - name: '[sig-compute][virtctl]create vm [test_id:9842]Complex example with inferred
        instancetype and preference'
      status: skipped
    - name: '[sig-compute][virtctl]create vm Complex example with memory'
      status: skipped
    - name: '[sig-compute][virtctl]create vm Complex example with sysprep volume'
      status: skipped
    - name: '[sig-compute][virtctl]create vm Complex example with generated cloud-init
        config'
      status: skipped
    - name: '[sig-compute][virtctl]create vm Complex example with access credentials'
      status: skipped
    - name: '[sig-compute][virtctl]create vm Failure of implicit inference does not
        fail the VM creation'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should migrate the source volume from
        a source DV to a destination PVC to a filesystem volume'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should migrate the source volume from
        a source DV to a destination PVC to a block volume'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should migrate the source volume from
        a source DV to a destination DV'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should migrate the source volume from
        a source and destination block RWX DVs'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should migrate the source volume from
        a block source and filesystem destination DVs'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should migrate a PVC with a VM using a
        containerdisk'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should cancel the migration by the reverting
        to the source volume'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should fail to migrate when the destination
        image is smaller'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should set the restart condition since
        the second volume is RWO and not part of the migration'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should refuse to restart the VM and set
        the ManualRecoveryRequired at VM shutdown'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Update volumes with
        the migration updateVolumesStrategy should cancel the migration and clear
        the volume migration state'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Hotplug volumes should
        be able to add and remove a volume with the volume migration feature gate
        enabled with a persistent volume'
      status: skipped
    - name: '[sig-storage] [Serial]Volumes update with migration Hotplug volumes should
        be able to add and remove a volume with the volume migration feature gate
        enabled with an ephemeral volume'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VirtualMachineInstances [test_id:7627]create
        a VirtualMachineInstance'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VirtualMachineInstances [test_id:7628]delete
        a VirtualMachineInstance'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VirtualMachineInstances [test_id:7629]update
        a VirtualMachineInstance'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VirtualMachineInstances [test_id:7630]patch
        a VirtualMachineInstance'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VirtualMachines [test_id:7631]create a
        VirtualMachine'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VirtualMachines [test_id:7632]delete a
        VirtualMachine'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VirtualMachines [test_id:7633]update a
        VirtualMachine'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VirtualMachines [test_id:7634]patch a VirtualMachine'
      status: skipped
    - name: '[sig-compute]Dry-Run requests Migrations [test_id:7635]create a migration'
      status: skipped
    - name: '[sig-compute]Dry-Run requests Migrations [test_id:7636]delete a migration'
      status: skipped
    - name: '[sig-compute]Dry-Run requests Migrations [test_id:7637]update a migration'
      status: skipped
    - name: '[sig-compute]Dry-Run requests Migrations [test_id:7638]patch a migration'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VMI Presets [test_id:7639]create a VMI
        preset'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VMI Presets [test_id:7640]delete a VMI
        preset'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VMI Presets [test_id:7641]update a VMI
        preset'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VMI Presets [test_id:7642]patch a VMI preset'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VMI ReplicaSets [test_id:7643]create a
        VMI replicaset'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VMI ReplicaSets [test_id:7644]delete a
        VMI replicaset'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VMI ReplicaSets [test_id:7645]update a
        VMI replicaset'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VMI ReplicaSets [test_id:7646]patch a VMI
        replicaset'
      status: skipped
    - name: '[sig-compute]Dry-Run requests KubeVirt CR [Serial][test_id:7648]delete
        a KubeVirt CR'
      status: skipped
    - name: '[sig-compute]Dry-Run requests KubeVirt CR [test_id:7649]update a KubeVirt
        CR'
      status: skipped
    - name: '[sig-compute]Dry-Run requests KubeVirt CR [test_id:7650]patch a KubeVirt
        CR'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VM Snapshots [test_id:7651]create a VM
        Snapshot'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VM Snapshots [test_id:7652]delete a VM
        Snapshot'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VM Snapshots [test_id:7653]update a VM
        Snapshot'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VM Snapshots [test_id:7654]patch a VM Snapshot'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VM Restores [test_id:7655]create a VM Restore'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VM Restores [test_id:7656]delete a VM Restore'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VM Restores [test_id:7657]update a VM Restore'
      status: skipped
    - name: '[sig-compute]Dry-Run requests VM Restores [test_id:7658]patch a VM Restore'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure tls configuration [test_id:9306]should
        result only connections with the correct client-side tls configurations are
        accepted by the components'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload [storage-req] Upload an image
        and start a VMI with PVC [test_id:4621] Should succeed DataVolume'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload [storage-req] Upload an image
        and start a VMI with PVC [test_id:4621] Should succeed PVC'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Create upload volume with force-bind
        flag Should succeed DataVolume'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Create upload volume with force-bind
        flag Should succeed PVC'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Create upload volume using
        volume-mode flag Should succeed [test_id:10671]block volumeMode'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Create upload volume using
        volume-mode flag Should succeed [test_id:10672]filesystem volumeMode'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Create upload volume using
        volume-mode flag [test_id:10674]Should fail with invalid volume-mode'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Upload fails when DV is in
        WFFC/PendingPopulation phase but uploads after consumer is created'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Create upload archive volume
        Should succeed DataVolume'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Create upload archive volume
        Should succeed PVC'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Upload fails Upload fails creating
        a DV when using a non-existent storageClass'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Upload fails Upload fails creating
        a PVC when using a non-existent storageClass'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Upload fails Upload doesn''t
        succeed when DV provisioning fails'
      status: skipped
    - name: '[sig-storage][Serial][virtctl]ImageUpload Upload fails Upload doesn''t
        succeed when PVC provisioning fails'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineInstancetype
        from v1beta1 without labels to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineInstancetype
        from v1beta1 with labels to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineInstancetype
        from v1alpha2 to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineInstancetype
        from v1alpha1 to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineInstancetypeSpecRevision
        v1alpha1 to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineClusterInstancetype
        from v1beta1 without labels to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineClusterInstancetype
        from v1beta1 with labels to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineClusterInstancetype
        from v1alpha2 to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineClusterInstancetype
        from v1alpha1 to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachinePreference
        from v1beta1 without labels to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachinePreference
        from v1beta1 with labels to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachinePreference
        from v1alpha2 to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachinePreference
        from v1alpha1 to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachinePreferenceSpecRevision
        v1alpha1 to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineClusterPreference
        from v1beta1 without labels to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineClusterPreference
        from v1beta1 with labels to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineClusterPreference
        from v1alpha2 to latest'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instance type and preference ControllerRevision Upgrades should upgrade VirtualMachineClusterPreference
        from v1alpha1 to latest'
      status: skipped
    - name: '[sig-compute][Serial]Instance Type and Preference Hotplug should plug
        extra resources from new instance type with maxGuest and maxSockets defined'
      status: skipped
    - name: '[sig-compute][Serial]Instance Type and Preference Hotplug should plug
        extra resources from new instance type without maxGuest and maxSockets defined'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with cni ptp plugin
        interface [test_id:1751]should create a virtual machine with one interface'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with cni ptp plugin
        interface [test_id:1752]should create a virtual machine with one interface
        with network definition from different namespace'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with cni ptp plugin
        interface [test_id:1753]should create a virtual machine with two interfaces'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with multus network
        as default network [test_id:1751]should create a virtual machine with one
        interface with multus default network definition'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with cni ptp plugin
        interface with custom MAC address [test_id:1705]should configure valid custom
        MAC address on ptp interface when using tuning plugin'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with Linux bridge
        plugin interface should be able to ping between two vms [test_id:1577]with
        secondary network only'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with Linux bridge
        plugin interface should be able to ping between two vms [test_id:1578]with
        default network and secondary network'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with Linux bridge
        plugin interface should be able to ping between two vms with default network
        and secondary network with IPAM'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with Linux bridge
        CNI plugin interface and custom MAC address. [test_id:676]should configure
        valid custom MAC address on Linux bridge CNI interface.'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. Single VirtualMachineInstance with Linux
        bridge CNI plugin interface [test_id:1756]should report all interfaces in
        Status'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. Single VirtualMachineInstance with Linux
        bridge CNI plugin interface should have the correct MTU on the secondary interface
        with no dhcp server'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. VirtualMachineInstance with invalid MAC
        address [test_id:1713]should failed to start with invalid MAC address'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        using different types of interfaces. Security Should allow outbound communication
        from VM under test - only if original MAC address is unchanged'
      status: skipped
    - name: '[sig-network] [Serial]Multus [rfe_id:1758][crit:medium][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        definition with qemu guest agent [test_id:1757] should report guest interfaces
        in VMI status'
      status: skipped
    - name: '[sig-compute]VM Affinity Updating VMs node affinity [test_id:11208]should
        successfully update node selector'
      status: skipped
    - name: '[sig-compute]VM Affinity Updating VMs node affinity [test_id:11209]should
        successfully update node affinity'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:526]given a vmi'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:527]given a vm'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin given a vmpool'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:528]given a vmi preset'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:529][crit:low]given
        a vmi replica set'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:3230]given a vmi
        migration'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:5243]given a vmsnapshot'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:5244]given a vmsnapshotcontent'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:5245]given a vmsrestore'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:TODO]given a virtualmachineinstancetype'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:TODO]given a virtualmachinepreference'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:TODO]given a virtualmachineclusterinstancetype'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        resources are correct for view, edit, and admin [test_id:TODO]given a virtualmachineclusterpreference'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default [test_id:3232]on
        vm start'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default [test_id:3233]on
        vm stop'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default [test_id:3234]on
        vm restart'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vm expand-spec'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vm portforward'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi guestosinfo'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi userlist'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi filesystemlist'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi addvolume'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi removevolume'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi freeze'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi unfreeze'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi softreboot'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi portforward'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi vsock'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on expand-vm-spec'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi sev/fetchcertchain'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi sev/querylaunchmeasurement'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi sev/setupsession'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi sev/injectlaunchsecret'
      status: skipped
    - name: '[rfe_id:500][crit:high][arm64][vendor:cnv-qe@redhat.com][level:component][sig-compute]User
        Access With default kubevirt service accounts should verify permissions on
        subresources are correct for view, edit, admin and default on vmi usbredir'
      status: skipped
    - name: '[sig-storage] [Serial]Backend Storage Should use RWO when RWX is not
        supported'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Soft
        reboot soft reboot vmi with agent connected should succeed'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Soft
        reboot soft reboot vmi with ACPI feature enabled should succeed'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Soft
        reboot soft reboot vmi neither have the agent connected nor the ACPI feature
        enabled should fail'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]Soft
        reboot soft reboot vmi should fail to soft reboot a paused vmi'
      status: skipped
    - name: '[sig-compute][Serial]Memory Hotplug A VM with memory liveUpdate enabled
        [test_id:10823]should successfully hotplug memory with a common VM'
      status: skipped
    - name: '[sig-compute][Serial]Memory Hotplug A VM with memory liveUpdate enabled
        [test_id:10823]should successfully hotplug memory with 2Mi pagesize hugepages
        VM'
      status: skipped
    - name: '[sig-compute][Serial]Memory Hotplug A VM with memory liveUpdate enabled
        [test_id:10824]after a hotplug memory and a restart the new memory value should
        be the base for the VM'
      status: skipped
    - name: '[sig-compute][Serial]Memory Hotplug A VM with memory liveUpdate enabled
        [test_id:10825]should successfully hotplug Memory and CPU in parallel'
      status: skipped
    - name: '[sig-compute][Serial]Memory Hotplug A VM with memory liveUpdate enabled
        should successfully hotplug memory when adding guest.memory to a VM'
      status: skipped
    - name: '[sig-compute][Serial]Memory Hotplug A VM with memory liveUpdate enabled
        should successfully hotplug memory twice'
      status: skipped
    - name: '[sig-compute][Serial]Memory Hotplug A VM with memory liveUpdate enabled
        should detect a failed memory hotplug'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype validation [test_id:CNV-9082] should
        allow valid instancetype'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype validation [test_id:CNV-9083] should
        reject invalid instancetype without CPU defined'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype validation [test_id:CNV-9083] should
        reject invalid instancetype without CPU.Guest defined'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype validation [test_id:CNV-9083] should
        reject invalid instancetype without Memory defined'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype validation [test_id:CNV-9083] should
        reject invalid instancetype without Memory.Guest defined'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Preference validation [test_id:CNV-9084] should
        allow valid preference'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VM with invalid InstancetypeMatcher [test_id:CNV-9086]
        should fail to create VM with non-existing cluster instancetype'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VM with invalid InstancetypeMatcher [test_id:CNV-9089]
        should fail to create VM with non-existing namespaced instancetype'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VM with invalid PreferenceMatcher [test_id:CNV-9091]
        should fail to create VM with non-existing cluster preference'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VM with invalid PreferenceMatcher [test_id:CNV-9090]
        should fail to create VM with non-existing namespaced preference'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences [Serial]with cluster memory overcommit being
        applied should apply memory overcommit instancetype to VMI even with cluster
        overcommit set'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9094]
        should find and apply cluster instancetype and preferences when kind isn''t
        provided'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9095]
        should apply instancetype and preferences to VMI'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application should
        apply memory overcommit instancetype to VMI'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9096]
        should fail if instancetype and VM define CPU'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9301]
        should fail if the VirtualMachine has  CPU resource requests'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9301]
        should fail if the VirtualMachine has  CPU resource limits'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9301]
        should fail if the VirtualMachine has  Memory resource requests'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9301]
        should fail if the VirtualMachine has  Memory resource limits'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9302]
        should apply preferences to default network interface'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9303]
        should apply preferences to default volume disks'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9098]
        should store and use ControllerRevisions of VirtualMachineInstancetypeSpec
        and VirtualMachinePreferenceSpec'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences Instancetype and preference application [test_id:CNV-9304]
        should fail if stored ControllerRevisions are different'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences with inferFromVolume should infer defaults from
        PersistentVolumeClaimVolumeSource'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences with inferFromVolume should infer defaults from
        existing DataVolume with labels'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences with inferFromVolume should infer defaults from
        DataVolumeTemplates and DataVolumeSourcePVC'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences with inferFromVolume should infer defaults from
        DataVolumeTemplates , DataVolumeSourceRef and DataSource'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences with inferFromVolume should infer defaults from
        DataVolumeTemplates , DataVolumeSourceRef and DataSource with labels'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences with inferFromVolume should ignore failure when
        trying to infer defaults from DataVolumeSpec with unsupported DataVolumeSource
        when policy is set'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences with inferFromVolume should reject VM creation
        when inference was successful but memory and RejectInferFromVolumeFailure
        were set with explicitly setting RejectInferFromVolumeFailure'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences with inferFromVolume should reject VM creation
        when inference was successful but memory and RejectInferFromVolumeFailure
        were set with implicitly setting RejectInferFromVolumeFailure (default)'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instance type with dedicatedCPUPlacement enabled
        should be accepted and result in running VirtualMachineInstance'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachineInstancetype v1alpha1 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachineInstancetype v1alpha2 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachineInstancetype v1beta1 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachineClusterInstancetype v1alpha1 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachineClusterInstancetype v1alpha2 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachineClusterInstancetype v1beta1 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachinePreference v1alpha1 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachinePreference v1alpha2 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachinePreference v1beta1 and fetch using v1alpha1, v1alpha2
        and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachineClusterPreference v1alpha1 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachineClusterPreference v1alpha2 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences instancetype.kubevirt.io apiVersion compatibility
        should create VirtualMachineClusterPreference v1beta1 and fetch using v1alpha1,
        v1alpha2 and v1beta1'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be accepted when VirtualMachineInstancetype meets CPU requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be accepted when VirtualMachineInstancetype meets Memory requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be accepted when VirtualMachine meets CPU (preferSockets default) requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be accepted when VirtualMachine meets CPU (preferCores) requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be accepted when VirtualMachine meets 1 vCPU requirement through defaults
        - bug #10047'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be accepted when VirtualMachine meets CPU (preferThreads) requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be accepted when VirtualMachine meets CPU (preferAny) requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be accepted when VirtualMachine meets Memory requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be rejected when VirtualMachineInstancetype does not meet CPU requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be rejected when VirtualMachineInstancetype does not meet Memory requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be rejected when VirtualMachine does not meet CPU (preferSockets default)
        requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be rejected when VirtualMachine does not meet CPU (preferCores) requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be rejected when VirtualMachine does not meet CPU (preferThreads) requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be rejected when VirtualMachine does not meet CPU (preferAny) requirements'
      status: skipped
    - name: '[crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]
        Instancetype and Preferences VirtualMachine using preference resource requirements
        should be rejected when VirtualMachine meets Memory requirements'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition set sidecar resources [test_id:3155][serial]should successfully
        start with hook sidecar annotation'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition with SM BIOS hook sidecar [test_id:3156]should successfully
        start with hook sidecar annotation for v1alpha2'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition with SM BIOS hook sidecar [test_id:3157]should call Collect
        and OnDefineDomain on the hook sidecar'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition with SM BIOS hook sidecar [test_id:3158]should update domain
        XML with SM BIOS properties'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition with SM BIOS hook sidecar should not start with hook sidecar
        annotation when the version is not provided'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition with sidecar-shim should receive Terminal signal on VMI deletion'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition with sidecar-shim migrate VMI with sidecar Fails to terminate
        on migration with < v1alpha3'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition with sidecar-shim migrate VMI with sidecar Terminates properly
        on migration with >= v1alpha3'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition with ConfigMap in sidecar hook annotation [test_id:9833]should
        update domain XML with SM BIOS properties when sidecar image is specified'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition with ConfigMap in sidecar hook annotation [test_id:9833]should
        update domain XML with SM BIOS properties when sidecar image is not specified'
      status: skipped
    - name: '[sig-compute]HookSidecars [rfe_id:2667][crit:medium][vendor:cnv-qe@redhat.com][level:component]
        VMI definition [Serial]with sidecar feature gate disabled [test_id:2666]should
        not start with hook sidecar annotation'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should apply the interface configuration'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection should have client server connectivity
        TCP Client server connectivity with a specific port number [IPv4]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection should have client server connectivity
        TCP Client server connectivity with a specific lower port number [IPv4]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection should have client server connectivity
        TCP Client server connectivity without a specific port number [IPv4]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection should have client server connectivity
        TCP Client server connectivity with a specific port number [IPv6]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection should have client server connectivity
        TCP Client server connectivity without a specific port number [IPv6]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection should have client server connectivity
        UDP Client server connectivity [IPv4]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection should have client server connectivity
        UDP Client server connectivity [IPv6]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection [outside_connectivity]should
        be able to reach the outside world [IPv4]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection [outside_connectivity]should
        be able to reach the outside world [IPv6]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection Connectivity should be preserved
        after migration [IPv4]'
      status: skipped
    - name: '[sig-network] [Serial] VirtualMachineInstance with passt network binding
        plugin should allow regular network connection Connectivity should be preserved
        after migration [IPv6]'
      status: skipped
    - name: '[sig-compute] Hyper-V enlightenments VMI with HyperV re-enlightenment
        enabled when TSC frequency is exposed on the cluster should be able to migrate'
      status: skipped
    - name: '[sig-compute] Hyper-V enlightenments VMI with HyperV re-enlightenment
        enabled when TSC frequency is exposed on the cluster should have TSC frequency
        set up in label and domain'
      status: skipped
    - name: '[sig-compute] Hyper-V enlightenments VMI with HyperV re-enlightenment
        enabled when [Serial] TSC frequency is not exposed on the cluster should be
        able to start successfully'
      status: skipped
    - name: '[sig-compute] Hyper-V enlightenments VMI with HyperV re-enlightenment
        enabled when [Serial] TSC frequency is not exposed on the cluster should be
        marked as non-migratable'
      status: skipped
    - name: '[sig-compute] Hyper-V enlightenments VMI with HyperV re-enlightenment
        enabled the vmi with HyperV feature matching a nfd label on a node should
        be scheduled'
      status: skipped
    - name: '[sig-compute] Hyper-V enlightenments VMI with HyperV re-enlightenment
        enabled [Serial] 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'
      status: skipped
    - name: '[sig-compute] Hyper-V enlightenments VMI with HyperV re-enlightenment
        enabled [Serial] 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 '
      status: skipped
    - name: '[sig-compute] Hyper-V enlightenments VMI with HyperV re-enlightenment
        enabled [Serial] the vmi with EVMCS HyperV feature should have correct HyperV
        and cpu features auto filled Verify that features aren''t applied when enabled
        is false'
      status: skipped
    - name: '[sig-compute] Hyper-V enlightenments VMI with HyperV passthrough should
        be usable and non-migratable'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [ref_id:2293] with
        a VMI running with an eviction strategy set [test_id:3242]should block the
        eviction api and migrate'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [ref_id:2293] with
        a VMI running with an eviction strategy set [sig-compute][test_id:3243]should
        recreate the PDB if VMIs with similar names are recreated'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [ref_id:2293] with
        a VMI running with an eviction strategy set should create the PDB if VMI is
        live-migratable and has the LiveMigrateIfPossible strategy set'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [ref_id:2293] with
        a VMI running with an eviction strategy set [sig-compute][test_id:7680]should
        delete PDBs created by an old virt-controller'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [ref_id:2293] with
        a VMI running with an eviction strategy set [test_id:3244]should block the
        eviction api while a slow migration is in progress'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [ref_id:2293] with
        a VMI running with an eviction strategy set [Serial] with node tainted during
        node drain [test_id:6982]should migrate a VMI only one time'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [ref_id:2293] with
        a VMI running with an eviction strategy set [Serial] with node tainted during
        node drain [test_id:2221] should migrate a VMI under load to another node'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [ref_id:2293] with
        a VMI running with an eviction strategy set [Serial] with node tainted during
        node drain [test_id:2222] should migrate a VMI when custom taint key is configured'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [ref_id:2293] with
        a VMI running with an eviction strategy set [Serial] with node tainted during
        node drain [test_id:2224] should handle mixture of VMs with different eviction
        strategies.'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration with a live-migrate eviction strategy set [Serial]with 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'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration [Serial] with a cluster-wide live-migrate eviction strategy
        set with a VMI running with no eviction strategy set [test_id:10155]should
        block the eviction api and migrate'
      status: skipped
    - name: '[rfe_id:393][crit:high][vendor:cnv-qe@redhat.com][level:system][sig-compute]
        Live Migration [Serial] with a cluster-wide live-migrate eviction strategy
        set with a VMI running with eviction strategy set to ''None'' [test_id:10156]The
        VMI should get evicted'
      status: skipped
    - name: '[sig-compute]Guest console log [level:component] Guest console log container
        set LogSerialConsole should successfully start with LogSerialConsole with
        AutoattachSerialConsole and LogSerialConsole'
      status: skipped
    - name: '[sig-compute]Guest console log [level:component] Guest console log container
        set LogSerialConsole should successfully start with LogSerialConsole with
        AutoattachSerialConsole but not LogSerialConsole'
      status: skipped
    - name: '[sig-compute]Guest console log [level:component] Guest console log container
        set LogSerialConsole should successfully start with LogSerialConsole without
        AutoattachSerialConsole but with LogSerialConsole'
      status: skipped
    - name: '[sig-compute]Guest console log [level:component] Guest console log container
        set LogSerialConsole should successfully start with LogSerialConsole without
        AutoattachSerialConsole and without LogSerialConsole'
      status: skipped
    - name: '[sig-compute]Guest console log [level:component] Guest console log container
        set LogSerialConsole it should exit cleanly when the shutdown is initiated
        by the guest'
      status: skipped
    - name: '[sig-compute]Guest console log [level:component] Guest console log container
        fetch logs it should fetch logs for a running VM with logs API'
      status: skipped
    - name: '[sig-compute]Guest console log [level:component] Guest console log container
        fetch logs it should rotate the internal log files'
      status: skipped
    - name: '[sig-compute]Guest console log [level:component] Guest console log container
        fetch logs it should not skip any log line even trying to flood the serial
        console for QOSGuaranteed VMs'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]IgnitionData
        [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A new
        VirtualMachineInstance with IgnitionData annotation with injected data [test_id:1616]should
        have injected data under firmware directory'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitNoCloud userDataBase64 source [test_id:1615]should
        have cloud-init data'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitNoCloud userDataBase64 source with
        injected ssh-key [test_id:1616]should have ssh-key under authorized keys'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitConfigDrive userDataBase64 source
        [test_id:3178]should have cloud-init data'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitConfigDrive userDataBase64 source
        with injected ssh-key [test_id:3178]should have ssh-key under authorized keys'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitConfigDrive userDataBase64 source
        cloud-init instance-id should be stable'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance should process provided cloud-init data [test_id:1617]
        with cloudInitNoCloud userData source'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance should process provided cloud-init data [test_id:3180]
        with cloudInitConfigDrive userData source'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance [test_id:1618]should take user-data from k8s secret'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitNoCloud networkData [test_id:3181]should
        have cloud-init network-config with NetworkData source'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitNoCloud networkData [test_id:3182]should
        have cloud-init network-config with NetworkDataBase64 source'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitNoCloud networkData [test_id:3183]should
        have cloud-init network-config from k8s secret'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitConfigDrive networkData [test_id:3184]should
        have cloud-init network-config with NetworkData source'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitConfigDrive networkData [test_id:4622]should
        have cloud-init meta_data with tagged devices'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitConfigDrive networkData [test_id:3185]should
        have cloud-init network-config with NetworkDataBase64 source'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitConfigDrive networkData [test_id:3186]should
        have cloud-init network-config from k8s secret'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitConfigDrive networkData [test_id:3187]should
        have cloud-init userdata and network-config from separate k8s secrets with
        lowercase labels'
      status: skipped
    - name: '[rfe_id:151][crit:high][vendor:cnv-qe@redhat.com][level:component][sig-compute]CloudInit
        UserData [rfe_id:151][crit:medium][vendor:cnv-qe@redhat.com][level:component]A
        new VirtualMachineInstance with cloudInitConfigDrive networkData [test_id:3187]should
        have cloud-init userdata and network-config from separate k8s secrets with
        camelCase labels'
      status: skipped
    - name: '[sig-compute]Pod Disruption Budget (PDB) should ensure the Pod Disruption
        Budget (PDB) is deleted when the VM is stopped via guest OS'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        CRD Validation [test_id:1595]Should reject POST if schema is invalid'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        CRD Validation [test_id:1596]should reject POST if validation webhoook deems
        the spec is invalid'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Preset Matching [test_id:1597]Should be accepted on POST'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Preset Matching [test_id:1598]Should reject a second submission of a VMIPreset'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Preset Matching [test_id:1599]Should return 404 if VMIPreset does not exist'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Preset Matching [test_id:1600]Should reject presets that conflict with VirtualMachineInstance
        settings'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Preset Matching [test_id:1601]Should accept presets that don''t conflict with
        VirtualMachineInstance settings'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Preset Matching [test_id:1602]Should ignore VMIs that don''t match'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Preset Matching [test_id:1603]Should not be applied to existing VMIs'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Exclusions [test_id:1604]Should not apply presets to VirtualMachineInstance''s
        with the exclusion marking'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Conflict [test_id:1605]should denied to start the VMI'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Override [test_id:644][rfe_id:609] should override presets'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Preset Lifecycle [test_id:617][rfe_id:609] should create and delete preset'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        Match Expressions [test_id:726] Should match multiple VMs via MatchExpression'
      status: skipped
    - name: '[rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VMIPreset
        [rfe_id:613]MatchLabels [test_id:672] Should match multiple VMs via MatchLabel'
      status: skipped
    - name: '[sig-compute]Configurations with all devices on the root PCI bus [test_id:4623]should
        start run the guest as usual'
      status: skipped
    - name: '[sig-compute]Configurations when requesting virtio-transitional models
        [test_id:6957]should start and run the guest'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]for
        CPU and memory limits should [test_id:3110]lead to get the burstable QOS class
        assigned when limit and requests differ'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]for
        CPU and memory limits should [test_id:3111]lead to get the guaranteed QOS
        class assigned when limit and requests are identical'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][vendor:cnv-qe@redhat.com][level:component]for
        CPU and memory limits should [test_id:3112]lead to get the guaranteed QOS
        class assigned when only limits are set'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with memory
        configuration provided by domain spec directly'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with memory
        configuration provided by resources limits'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with memory
        configuration provided by resources requests and limits'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:2065][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        3 CPU cores [test_id:1659]should report 3 cpu cores under guest OS'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:2065][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        3 CPU cores [test_id:4624]should set a correct memory units'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:2065][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        3 CPU cores [test_id:1660]should report 3 sockets under guest OS'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:2065][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        3 CPU cores [test_id:1661]should report 2 sockets from spec.domain.resources.requests
        under guest OS '
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:2065][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        3 CPU cores [test_id:1662]should report 2 sockets from spec.domain.resources.limits
        under guest OS '
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:2065][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        3 CPU cores [test_id:1663]should report 4 vCPUs under guest OS'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:2065][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        3 CPU cores [Serial][test_id:1664]should map cores to virtio block queues'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:2065][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        3 CPU cores [test_id:1665]should map cores to virtio net queues'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:2065][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        3 CPU cores [test_id:1667]should not enforce explicitly rejected virtio block
        queues without cores'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        no memory requested [test_id:3113]should failed to the VMI creation'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial][rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        cluster memory overcommit being applied [test_id:3114]should set requested
        amount of memory according to the specified virtual memory'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with BIOS
        bootloader method and no disk [test_id:5265]should find no bootable device
        by default'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with BIOS
        bootloader method and no disk [test_id:5266]should boot to NIC rom if a boot
        order was set on a network interface'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with ACPI
        SLIC table Should configure guest APCI SLIC with Secret file'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:2262][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        EFI bootloader method [Serial][test_id:1668]should use EFI without secure
        boot'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:2262][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        EFI bootloader method [Serial][test_id:4437]should enable EFI secure boot'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        diverging guest memory from requested memory [test_id:1669]should show the
        requested guest memory inside the VMI'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        diverging memory limit from memory request and no guest memory [test_id:3115]should
        show the memory request inside the VMI'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:989]test
        cpu_allocation_ratio virt-launchers pod cpu requests should be proportional
        to the number of vCPUs'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        support memory over commitment [test_id:755]should show the requested memory
        different than guest memory'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component]Support
        memory over commitment test [test_id:730]Check OverCommit VM Created and Started'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component]Support
        memory over commitment test [test_id:731]Check OverCommit status on VMI'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:609][crit:medium][vendor:cnv-qe@redhat.com][level:component]Support
        memory over commitment test [test_id:732]Check Free memory on the VMI'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:3078][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        usb controller [test_id:3117]should start the VMI with usb controller when
        usb device is present'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:3078][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        usb controller [test_id:3117]should start the VMI with usb controller when
        input device doesn''t have bus'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:3078][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        usb controller [test_id:3118]should start the VMI without usb controller'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:3077][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        input devices [test_id:2642]should failed to start the VMI with wrong type
        of input device'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:3077][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        input devices [test_id:3074]should failed to start the VMI with wrong bus
        of input device'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:3077][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        input devices [test_id:3072]should start the VMI with tablet input device
        with virtio bus'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:3077][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        input devices [test_id:3073]should start the VMI with tablet input device
        with usb bus'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with namespace
        different from provided should fail admission'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        hugepages should consume hugepages  [Serial][test_id:1671]hugepages-2Mi'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        hugepages should consume hugepages  [Serial][test_id:1672]hugepages-1Gi'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        hugepages should consume hugepages  [Serial][test_id:1672]hugepages-2Mi with
        guest memory set explicitly'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        hugepages with unsupported page size [test_id:1673]should failed to schedule
        the pod'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:893][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        rng [test_id:1674]should have the virtio rng device present when present'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:893][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        rng [test_id:1675]should not have the virtio rng device when not present'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [test_id:1676]should have attached a guest agent channel by default'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [test_id:1677]VMI condition should signal agent presence'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [test_id:4625]should remove condition when agent is off'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [Serial]with cluster config changes [test_id:5267]VMI condition
        should signal unsupported agent presence'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [Serial]with cluster config changes [test_id:6958]VMI condition
        should not signal unsupported agent presence for optional commands'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [test_id:4626]should have guestosinfo in status when agent is present'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [test_id:4627]should return the whole data when agent is present'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [test_id:4628]should not return the whole data when agent is not
        present'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [test_id:4629]should return user list'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        guestAgent [test_id:4630]should return filesystem list'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        serial-number [test_id:3121]should have serial-number set when present'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        serial-number [test_id:3122]should not have serial-number set when not present'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with TSC
        timer [test_id:6843]should set a TSC fequency and have the CPU flag avaliable
        in the guest'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with Clock
        and timezone [sig-compute][test_id:5268]guest should see timezone'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition with volumes,
        disks and filesystem defined [test_id:6960]should reject disk with missing
        volume'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial]using
        defaultRuntimeClass configuration should apply runtimeClassName to pod when
        set'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition should
        not apply runtimeClassName to pod when not set'
      status: skipped
    - name: '[sig-compute]Configurations VirtualMachineInstance definition [Serial]with
        geust-to-request memory  should add guest-to-memory headroom'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        CPU spec [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]when
        CPU model defined [test_id:1678]should report defined CPU model'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        CPU spec [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]when
        CPU model equals to passthrough [test_id:1679]should report exactly the same
        model as node CPU'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        CPU spec [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]when
        CPU model not defined [test_id:1680]should report CPU model from libvirt capabilities'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        CPU spec when CPU features defined [test_id:3123]should start a Virtual Machine
        with matching features'
      status: skipped
    - name: '[sig-compute]Configurations [Serial][rfe_id:2869][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        machine type settings [test_id:3124]should set machine type from VMI spec'
      status: skipped
    - name: '[sig-compute]Configurations [Serial][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'
      status: skipped
    - name: '[sig-compute]Configurations [Serial][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'
      status: skipped
    - name: '[sig-compute]Configurations [Serial][rfe_id:2869][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        machine type settings [Serial][test_id:3126]should set machine type from kubevirt-config'
      status: skipped
    - name: '[sig-compute]Configurations with a custom scheduler [test_id:4631]should
        set the custom scheduler on the pod'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        CPU request settings [test_id:3127]should set CPU request from VMI spec'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        CPU request settings [test_id:3128]should set CPU request when it is not provided'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:140][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        CPU request settings [Serial][test_id:3129]should set CPU request from kubevirt-config'
      status: skipped
    - name: '[sig-compute]Configurations [Serial]with automatic CPU limit configured
        in the CR should not set a CPU limit if the namespace doesn''t match the selector'
      status: skipped
    - name: '[sig-compute]Configurations [Serial]with automatic CPU limit configured
        in the CR should set a CPU limit if the namespace matches the selector'
      status: skipped
    - name: '[sig-compute]Configurations with automatic resource limits FG enabled
        when there is no ResourceQuota with memory and cpu limits associated with
        the creation namespace [test_id:11215]should not automatically set memory
        limits in the virt-launcher pod'
      status: skipped
    - name: '[sig-compute]Configurations with automatic resource limits FG enabled
        when a ResourceQuota with memory and cpu limits is associated to the creation
        namespace [test_id:11214]should set cpu and memory limit in the virt-launcher
        pod'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:904][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        driver cache and io settings and PVC [test_id:1681]should set appropriate
        cache modes'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:904][crit:medium][vendor:cnv-qe@redhat.com][level:component]with
        driver cache and io settings and PVC [test_id:5360]should set appropriate
        IO modes'
      status: skipped
    - name: '[sig-compute]Configurations Block size configuration set [test_id:6965]Should
        set BlockIO when using custom block sizes'
      status: skipped
    - name: '[sig-compute]Configurations Block size configuration set [test_id:6966]Should
        set BlockIO when set to match volume block sizes on block devices'
      status: skipped
    - name: '[sig-compute]Configurations Block size configuration set [test_id:6967]Should
        set BlockIO when set to match volume block sizes on files'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:898][crit:medium][vendor:cnv-qe@redhat.com][level:component]New
        VirtualMachineInstance with all supported drives [test_id:1682]should have
        all the device nodes'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:898][crit:medium][vendor:cnv-qe@redhat.com][level:component]New
        VirtualMachineInstance with all supported drives [test_id:3906]should configure
        custom Pci address'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:898][crit:medium][vendor:cnv-qe@redhat.com][level:component]New
        VirtualMachineInstance with all supported drives [test_id:1020]should not
        create the VM with wrong PCI address'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:1684]should set
        the cpumanager label to false when it''s not running'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:1685]non master
        node should have a cpumanager label'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:991]should be scheduled
        on a node with running cpu manager'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]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'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:4023]should start
        a vmi with dedicated cpus and isolated emulator thread  with explicit resources
        set'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:4023]should start
        a vmi with dedicated cpus and isolated emulator thread without resource requirements
        set'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:4024]should fail
        the vmi creation if IsolateEmulatorThread requested without dedicated cpus'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:802]should configure
        correct number of vcpus with requests.cpus'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:1688]should fail
        the vmi creation if the requested resources are inconsistent'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:1689]should fail
        the vmi creation if cpu is not an integer'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:1690]should fail
        the vmi creation if Guaranteed QOS cannot be set'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]with cpu pinning enabled [test_id:830]should start
        a vm with no cpu pinning after a vm with cpu pinning on same node'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]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'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:897][crit:medium][arm64][vendor:cnv-qe@redhat.com][level:component]VirtualMachineInstance
        with CPU pinning [Serial]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'
      status: skipped
    - name: '[sig-compute]Configurations [rfe_id:2926][crit:medium][vendor:cnv-qe@redhat.com][level:component]Check
        Chassis value [Serial][test_id:2927]Test Chassis value in a newly created
        VM'
      status: skipped
    - name: '[sig-compute]Configurations [Serial][rfe_id:2926][crit:medium][vendor:cnv-qe@redhat.com][level:component]Check
        SMBios with default and custom values [test_id:2751]test default SMBios'
      status: skipped
    - name: '[sig-compute]Configurations [Serial][rfe_id:2926][crit:medium][vendor:cnv-qe@redhat.com][level:component]Check
        SMBios with default and custom values [test_id:2752]test custom SMBios values'
      status: skipped
    - name: '[sig-compute]Configurations With ephemeral CD-ROM For various bus types
        [test_id:3777] Should be accepted when using sata'
      status: skipped
    - name: '[sig-compute]Configurations With ephemeral CD-ROM For various bus types
        [test_id:3809] Should be accepted when using scsi'
      status: skipped
    - name: '[sig-compute]Configurations With ephemeral CD-ROM For various bus types
        [test_id:3776] Should be rejected when using virtio'
      status: skipped
    - name: '[sig-compute]Configurations With ephemeral CD-ROM For various bus types
        [test_id:3808] Should be rejected when using ide'
      status: skipped
    - name: '[sig-compute]Configurations Custom PCI Addresses configuration should
        configure custom pci address [Serial][test_id:5269]across all available PCI
        root bus slots'
      status: skipped
    - name: '[sig-compute]Configurations Custom PCI Addresses configuration should
        configure custom pci address [test_id:5270]across all available PCI functions
        of a single slot'
      status: skipped
    - name: '[sig-compute]Configurations Check KVM CPUID advertisement [test_id:5271]test
        cpuid hidden'
      status: skipped
    - name: '[sig-compute]Configurations Check KVM CPUID advertisement [test_id:5272]test
        cpuid default'
      status: skipped
    - name: '[sig-compute]Configurations virt-launcher processes memory usage should
        be lower than allocated size'
      status: skipped
    - name: '[sig-compute]Configurations When topology spread constraints are defined
        for the VMI they should be applied to the launcher pod'
      status: skipped
    - name: '[sig-compute] VMIDefaults Disk defaults [test_id:4115]Should be applied
        to VMIs'
      status: skipped
    - name: '[sig-compute] VMIDefaults Disk defaults [test_id:]Should be applied to
        any auto attached volume disks'
      status: skipped
    - name: '[sig-compute] VMIDefaults MemBalloon defaults [test_id:4556]Should be
        present in domain'
      status: skipped
    - name: '[sig-compute] VMIDefaults MemBalloon defaults [Serial]Should override
        period in domain if present in virt-config  [test_id:4557]with period 12'
      status: skipped
    - name: '[sig-compute] VMIDefaults MemBalloon defaults [Serial]Should override
        period in domain if present in virt-config  [test_id:4558]with period 0'
      status: skipped
    - name: '[sig-compute] VMIDefaults MemBalloon defaults [test_id:4559]Should not
        be present in domain '
      status: skipped
    - name: '[sig-compute] VMIDefaults Input defaults [test_id:TODO]Should be set
        in VirtualMachineInstance'
      status: skipped
    - name: '[sig-compute] VMIDefaults Input defaults [test_id:TODO]Should be applied
        to a device added by AutoattachInputDevice'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints [test_id:4136] should find one leading virt-controller and two ready'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints [test_id:4137]should find one leading virt-operator and two ready'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints [test_id:4138]should be exposed and registered on the metrics endpoint'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints [test_id:4139]should return Prometheus metrics'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should throttle the Prometheus metrics access [test_id:4140] by
        using IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should throttle the Prometheus metrics access [test_id:6226] by
        using IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the metrics for a running VM [test_id:4141] by using
        IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the metrics for a running VM [test_id:6227] by using
        IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:4142]
        storage flush requests metric by using IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:6228]
        storage flush requests metric by using IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:4142]
        time spent on cache flushing metric by using IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:6229]
        time spent on cache flushing metric by using IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:4142]
        I/O read operations metric by using IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:6230]
        I/O read operations metric by using IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:4142]
        I/O write operations metric by using IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:6231]
        I/O write operations metric by using IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:4142]
        storage read operation time metric by using IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:6232]
        storage read operation time metric by using IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:4142]
        storage read traffic in bytes metric by using IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:6233]
        storage read traffic in bytes metric by using IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:4142]
        storage write operation time metric by using IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:6234]
        storage write operation time metric by using IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:4142]
        storage write traffic in bytes metric by using IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include the storage metrics for a running VM [test_id:6235]
        storage write traffic in bytes metric by using IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:4143] network metrics
        by IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:6236] network metrics
        by IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:4144] memory metrics
        by IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:6237] memory metrics
        by IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:4553] vcpu wait
        by IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:6238] vcpu wait
        by IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:4554] vcpu seconds
        by IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:6239] vcpu seconds
        by IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:4556] vmi unused
        memory by IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include metrics for a running VM [test_id:6240] vmi unused
        memory by IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include VMI infos for a running VM [test_id:4145] by IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include VMI infos for a running VM [test_id:6241] by IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include VMI phase metrics for all running VMs [test_id:4146]
        by IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include VMI phase metrics for all running VMs [test_id:6242]
        by IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include VMI eviction blocker status for all running VMs [test_id:4148]
        by IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include VMI eviction blocker status for all running VMs [test_id:6243]
        by IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include kubernetes labels to VMI metrics [test_id:4147] by
        IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include kubernetes labels to VMI metrics [test_id:6244] by
        IPv6'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include swap metrics [test_id:4555] by IPv4'
      status: skipped
    - name: '[Serial][sig-compute]Infrastructure [rfe_id:3187][crit:medium][vendor:cnv-qe@redhat.com][level:component]Prometheus
        Endpoints should include swap metrics [test_id:6245] by IPv6'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given cpu/memory in requests/limits should allow int
        type'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given cpu/memory in requests/limits should allow float
        type'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:3161]should carry vm.template.spec.annotations
        to VMI and ignore vm ones'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should sync the generation annotation on the
        vmi during restarts'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should not update the vmi generation annotation
        when the template changes'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1521]should remove VirtualMachineInstance
        once the VM is marked for deletion with ContainerDisk'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1521]should remove VirtualMachineInstance
        once the VM is marked for deletion [storage-req]with Filesystem Disk'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1521]should remove VirtualMachineInstance
        once the VM is marked for deletion [storage-req]with Block Disk'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1522]should remove owner references
        on the VirtualMachineInstance if it is orphan deleted'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1523]should recreate VirtualMachineInstance
        if it gets deleted'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1524]should recreate VirtualMachineInstance
        if the VirtualMachineInstance''s pod gets deleted'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1525]should stop VirtualMachineInstance
        if running set to false with ContainerDisk'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1525]should stop VirtualMachineInstance
        if running set to false [storage-req]with Filesystem Disk'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1525]should stop VirtualMachineInstance
        if running set to false [storage-req]with Block Disk'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1526]should start and stop VirtualMachineInstance
        multiple times'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1527]should not update the VirtualMachineInstance
        spec if Running'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:1528]should survive guest shutdown,
        multiple times'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should always have updated vm revision when starting
        vm'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:4645]should set the Ready condition
        on VM'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should report an error status [test_id:6867]
        when VM scheduling error occurs with unsatisfiable resource requirements'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should report an error status [test_id:6868]
        when VM scheduling error occurs with unsatisfiable scheduling constraints'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should report an error status [test_id:7596]
        when a VM with a missing PVC is started'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should report an error status [test_id:7597]
        when a VM with a missing DV is started'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:6869]should report an error status when
        image pull error occurs'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:7679]should report an error status when
        data volume error occurs'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should stop a running VM [test_id:3163]with RunStrategyAlways'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should stop a running VM [test_id:2186]with RunStrategyRerunOnFailure'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should stop a running VM [test_id:2189]with RunStrategyManual'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should restart a running VM [test_id:3164]with
        RunStrategyAlways'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should restart a running VM [test_id:2187]with
        RunStrategyRerunOnFailure'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should restart a running VM [test_id:2035]with
        RunStrategyManual'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should start a stopped VM [test_id:2036]with
        RunStrategyManual'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should start a stopped VM [test_id:2037]with
        RunStrategyHalted'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should not remove a succeeded VMI with RunStrategyOnce'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given should not remove a succeeded VMI [test_id:2190]
        with RunStrategyManual'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given [test_id:6311]should start in paused state using
        RunStrategyManual'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given Using RunStrategyAlways [test_id:3165]should
        restart a succeeded VMI'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given Using RunStrategyAlways [test_id:4119]should
        migrate a running VM'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given Using RunStrategyAlways [test_id:7743]should
        not migrate a running vm if dry-run option is passed'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given Using RunStrategyRerunOnFailure [test_id:2188]
        should remove a succeeded VMI'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given Using RunStrategyRerunOnFailure should restart
        a failed VMI'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given Using RunStrategyOnce Should leave a failed VMI'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given Using RunStrategyOnce with a failing VMI and
        the kubevirt.io/keep-launcher-alive-after-failure annotation [test_id:7164]VMI
        launcher pod should fail'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        A valid VirtualMachine given Using RunStrategyOnce with a failing VMI and
        the kubevirt.io/keep-launcher-alive-after-failure annotation [test_id:6993]VMI
        launcher pod compute container should keep running'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        [rfe_id:273]with oc/kubectl [release-blocker][test_id:299]should create VM
        via command line using all supported API versions with v1 api'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        [rfe_id:273]with oc/kubectl [release-blocker][test_id:299]should create VM
        via command line using all supported API versions with v1alpha3 api'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        [rfe_id:273]with oc/kubectl [test_id:264]should create and delete a VM'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        [rfe_id:273]with oc/kubectl should not change anything if dry-run option is
        passed [test_id:7530]when starting a VM'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        [rfe_id:273]with oc/kubectl should not change anything if dry-run option is
        passed when stopping a VM [test_id:7529]with no other flags'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        [rfe_id:273]with oc/kubectl should not change anything if dry-run option is
        passed when stopping a VM [test_id:7604]with grace period'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        [rfe_id:273]with oc/kubectl should not change anything if dry-run option is
        passed [test_id:7528]when restarting a VM'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        crash loop backoff should backoff attempting to create a new VMI when ''runStrategy:
        Always'' during crash loop.'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        crash loop backoff should be able to stop a VM during crashloop backoff when
        when ''runStrategy: Always'' is set'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        VirtualMachineControllerFinalizer should be added when the vm is created and
        removed when the vm is being deleted'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        VirtualMachineControllerFinalizer should be removed when the vm has child
        resources, such as instance type ControllerRevisions, that have been deleted
        before the vm - issue #9438'
      status: skipped
    - name: '[rfe_id:1177][crit:medium][vendor:cnv-qe@redhat.com][level:component][sig-compute]VirtualMachine
        [Serial] when node becomes unhealthy [Serial] the VMs running in that node
        should be respawned'
      status: skipped
    - name: '[sig-performance][Serial] CPU latency tests for measuring realtime VMs
        performance running cyclictest and collecting results directly from VM'
      status: skipped
    - name: '[sig-storage] [Serial]SCSI persistent reservation Use LUN disk with presistent
        reservation Should successfully start a VM with persistent reservation'
      status: skipped
    - name: '[sig-storage] [Serial]SCSI persistent reservation Use LUN disk with presistent
        reservation Should successfully start 2 VMs with persistent reservation on
        the same LUN'
      status: skipped
    - name: '[sig-storage] [Serial]SCSI persistent reservation with PersistentReservation
        feature gate toggled should delete and recreate virt-handler'
      status: skipped
    - name: '[sig-performance][Serial] Control Plane Performance Density Testing Density
        test [small] create a batch of 100 VMIs should sucessfully create all VMIS'
      status: skipped
    - name: '[sig-performance][Serial] Control Plane Performance Density Testing Density
        test [small] create a batch of 100 running VMs should sucessfully create all
        VMS'
      status: skipped
    - name: '[sig-performance][Serial] Control Plane Performance Density Testing Density
        test [small] create a batch of 100 running VMs using a single instancetype
        and preference should sucessfully create all VMS with instancetype and preference'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        Multiple virtual machines connectivity using bridge binding interface with
        a test outbound VMI should be able to reach [test_id:1539]the Inbound VirtualMachineInstance'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        Multiple virtual machines connectivity using bridge binding interface with
        a test outbound VMI should be able to reach [test_id:1540]the Inbound VirtualMachineInstance
        with pod network connectivity explicitly set'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        Multiple virtual machines connectivity using bridge binding interface with
        a test outbound VMI should be able to reach [test_id:1541]the Inbound VirtualMachineInstance
        with custom MAC address'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        Multiple virtual machines connectivity using bridge binding interface with
        propagated IP from a pod should be able to reach [test_id:1543]on the same
        node from Pod'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        Multiple virtual machines connectivity using bridge binding interface with
        propagated IP from a pod should be able to reach [test_id:1544]on a different
        node from Pod'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        Multiple virtual machines connectivity using bridge binding interface with
        propagated IP from a pod should be able to reach [test_id:1545]on the same
        node from Node'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        Multiple virtual machines connectivity using bridge binding interface with
        propagated IP from a pod should be able to reach [test_id:1546]on a different
        node from Node'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        Multiple virtual machines connectivity using bridge binding interface VirtualMachineInstance
        with default interface model [test_id:1550]should expose the right device
        type to the guest'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with custom interface model [test_id:1770]should expose
        the right device type to the guest'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with disabled automatic attachment of interfaces [test_id:1774]should
        not configure any external interfaces'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with disabled automatic attachment of interfaces [test_id:1775]should
        start a VMI with no network'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VMI with an interface that has ACPI Index set'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with learning disabled on pod interface [test_id:1777]should
        disable learning on pod iface'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with dhcp options [test_id:1778]should offer extra
        dhcp options to pod iface'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with custom dns [test_id:1779]should have custom resolv.conf'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection ipv4 with a specific port number [IPv4]'
      status: passed
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection ipv4 with a specific port used by live migration'
      status: passed
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection ipv4 without a specific port number [IPv4]'
      status: passed
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection ipv4 with custom CIDR [IPv4]'
      status: passed
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection ipv4 with custom CIDR [IPv4] containing leading
        zeros'
      status: passed
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection [outside_connectivity]should be able to reach
        the outside world [IPv4]'
      status: passed
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection IPv6 with a specific port number [IPv6]'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection IPv6 with a specific port used by live migration'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection IPv6 without a specific port number [IPv6]'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection IPv6 with custom CIDR [IPv6]'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism [Conformance][test_id:1780][label:masquerade_binding_connectivity]should
        allow regular network connection [outside_connectivity]should be able to reach
        the outside world [IPv6]'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism when performing migration
        [Conformance] preserves connectivity - IPv4 without a specific port number'
      status: passed
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism when performing migration
        [Conformance] preserves connectivity - IPv4 with explicit ports used by live
        migration'
      status: passed
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism when performing migration
        [Conformance] should preserve connectivity - IPv6'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism MTU verification
        should have the correct MTU IPv4'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with masquerade binding mechanism MTU verification
        should have the correct MTU IPv6'
      status: skipped
    - name: '[sig-network] [rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking
        VirtualMachineInstance with TX offload disabled [test_id:1781]should have
        tx checksumming disabled on interface serving dhcp'
      status: skipped
