Description of problem:
We should enforce the conventions mentioned in https://github.com/openshift/enhancements/pull/763 via a test in origin.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
There's one more case where this is failing, see https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/26054/pull-ci-openshift-origin-master-e2e-gcp/1390366748154269696
It failed on:
May 6 19:42:46.977: FAIL:
1 pods found with invalid tolerations:
Verified bug in the link below and i see that test "Managed cluster should ensure platform components have system-* priority class associated" has been flaking from last 2 days. Based on that moving the bug to verified state.
Moving back to post, because this hasn't been backported, and I want to attach a follow-up PR.
Occasional hits still in CI:
$ curl -s 'https://search.ci.openshift.org/search?search=pods+found+with+invalid+priority+class&maxAge=96h&context=4&type=junit' | jq -r 'to_entries.value | to_entries.value.context' | sed -n 's/\(.*\)-[a-z0-9]*\( (currently.*\)/\1...\2/p' | sort | uniq -c
1 kube-system/openvpn-client-649bcb9d98... (currently "")
12 openshift-infra/recycler-for-nfs... (currently "")
Maybe those are non-core components that need carve-outs?
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 Container Platform 4.8.2 bug fix and security 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.