Bug 1876475

+++ This bug was initially created as a clone of Bug #1869527 +++

Description of problem:
Disk io can't worked if namespace have label
mutatevirtualmachines.kubemacpool.io: allocate

Version-Release number of selected component (if applicable):
2.4.1

How reproducible:
always

Steps to Reproduce:
1. create a namespace with label kubemacpool
$ oc describe namespace virt-general-disk-io-option
Name:         virt-general-disk-io-option
Labels:       mutatevirtualmachines.kubemacpool.io=allocate
Annotations:  openshift.io/description:
              openshift.io/display-name:
              openshift.io/requester: unprivileged-user
              openshift.io/sa.scc.mcs: s0:c25,c10
              openshift.io/sa.scc.supplemental-groups: 1000620000/10000
              openshift.io/sa.scc.uid-range: 1000620000/10000
Status:       Active

No resource quota.

No LimitRange resource.

2. create a vm with disk io configuration
$cat vm.yaml
....
        devices:
          disks:
          - disk:
              bus: virtio
            io: native
            name: containerdisk
....
$oc create -f vm.yaml
3.check vm 
$oc get vm -o yaml
....
            - disk:
                bus: virtio
              name: containerdisk
          machine:
            type: pc-q35-rhel8.2.0
....
Actual results:
no disk io configuration

Expected results:
should have disk io
...
            - disk:
                bus: virtio
              io: native
              name: containerdisk
          machine:
            type: pc-q35-rhel8.2.0
...
Additional info:
if remove the label of namespace and create vm, disk io worked well.