We need our platform components to set the system-cluster-critical priorityClassName on their workloads. More detail here: https://github.com/openshift/origin/pull/22217 For service catalog this means updating the deployments that generate these pods: openshift-svcat-apiserver-operator/openshift-svcat-apiserver-operator-586bd7dc64-vl2qt, openshift-svcat-controller-manager-operator/openshift-svcat-controller-manager-operator-7f8fbc8fb4-8bwbx Note: the test in the linked PR above runs on what is installed by default, so it is only flagging the svc catalog operators. But when service catalog is enabled we need to ensure the actual apiserver and controller manager pods are also running with system-cluster-critical priority class.
fixed by https://github.com/openshift/cluster-svcat-apiserver-operator/pull/36 and https://github.com/openshift/cluster-svcat-controller-manager-operator/pull/23
The current payload doesn't include the fixed PR, change status to MODIFIED. Cluster version is 4.0.0-0.nightly-2019-03-06-074438
LGTM, verify it. Current version: 4.0.0-0.nightly-2019-03-13-233958 [jzhang@dhcp-140-18 ocp14]$ oc get pods -o yaml -n openshift-service-catalog-controller-manager-operator |grep priority priority: 2000000000 priorityClassName: system-cluster-critical [jzhang@dhcp-140-18 ocp14]$ oc get pods -o yaml -n openshift-service-catalog-apiserver-operator |grep priority priority: 2000000000 priorityClassName: system-cluster-critical [jzhang@dhcp-140-18 ocp14]$ oc get pods -o yaml -n openshift-service-catalog-apiserver |grep priority priority: 2000000000 priorityClassName: system-cluster-critical [jzhang@dhcp-140-18 ocp14]$ oc get pods -o yaml -n openshift-service-catalog-controller-manager |grep priority priority: 2000000000 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, 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/RHBA-2019:0758