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:
Started the PR: https://github.com/kubevirt/ssp-operator/pull/169
PR got merged upstream
Should be available in kubevirt-ssp-operator-container-v4.9.0-10 https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1675584
Verified on ssp-operator-version: v4.9.0-16 value on pods ssp-operator + virt-template-validator is set to -> priorityClassName: system-cluster-critical
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.9.0 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:4104