Description of problem: OCP has changed the names of priority classes. This component's _infrastructure pods_ priority classes should be added or adjusted accordingly to either system-cluster-critical or system-node-critical priority. See https://mailman-int.corp.redhat.com/archives/aos-devel/2021-April/msg00402.html The new classes must not be set on user workloads (i.e. VMs) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Infrastructure components should carry the new priority classes Additional info:
Adding Priority Class to network components PRs: https://github.com/kubevirt/cluster-network-addons-operator/pull/907 https://github.com/kubevirt/cluster-network-addons-operator/pull/908 https://github.com/kubevirt/cluster-network-addons-operator/pull/909 https://github.com/k8snetworkplumbingwg/kubemacpool/pull/317 https://github.com/nmstate/kubernetes-nmstate/pull/780 https://github.com/kubevirt/bridge-marker/pull/26 https://github.com/k8snetworkplumbingwg/ovs-cni/pull/172 https://github.com/kubevirt/macvtap-cni/pull/42
Verified on: kubevirt-hyperconverged-operator - v.4.8.1 CNV - v.4.8.0 OCP - v.4.8.4 Kubernetes Version: v1.21.1+38b3ecc Fix was verified on the following components: - cluster-network-addons-operator - bridge-marker - kube-cni-linux-bridge-plugin - kubemacpool-mac-controller-manager - kubemacpool-cert-manager - nmstate-cert-manager - nmstate-handler - nmstate-webhook - ovs-cni-amd64 These components were fixed, but cannot be verified on in D/S version: - macvtap-cni - multus
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 (Moderate: OpenShift Virtualization 4.8.1 Images security and bug fix update), 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-2021:3259