Description of problem: When node doesn't have a kvm device, node labeller stays in a pending state. How reproducible: 100% Steps to Reproduce: 1. Deploy labeller on the node which doesn't have kvm device Actual results: Labeller is in pending state Expected results: Labeller runs, or is not scheduled
This will fix it: https://github.com/MarSik/kubevirt-ssp-operator/pull/181 That PR deletes the node kvm device requirement (devices.kubevirt.io/kvm: "1"). Instead it tries to mount kvm device inside the container. If kvm is not available, container exits with 0 and no labels are added. If kvm is available it continues as usual (gather supported cpu, hyperv features and labels the node)
Node labeller is not on pending in case of no kvm devices. Verify with: Cluster version is 4.5.0-rc.7 kubevirt: v0.30.3 CNV 2.4
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3194