Job failed on elease-openshift-ocp-installer-e2e-aws-4.5:
There seems to also be a fail in a seemingly related test:
[sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] [Top Level] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD without validation schema [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]
Note the "without"
The test is consistently failing.
Job view: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-old-rhcos-e2e-aws-4.3/415
hopefully this fix also resolves:
[sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] [Top Level] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance]
yes, it applies to all "CustomResourcePublishOpenAPI [Privileged:ClusterAdmin]" tests, it looks promissing for 4.5 - https://testgrid.k8s.io/redhat-openshift-ocp-release-4.5-blocking#release-openshift-origin-installer-e2e-gcp-4.5&sort-by-flakiness
[build-cop] still seeing this in 4.4 branch CIs even though the fix merged 13 hours ago
From https://testgrid.k8s.io/redhat-openshift-ocp-release-4.4-blocking#release-openshift-origin-installer-e2e-gcp-4.4&sort-by-flakiness view, searching the keywords 'works for CRD with validation schema' on page, we can see the test '[sig-api-machinery] CustomResourcePublishOpenAPI [Feature:CustomResourcePublishOpenAPI]' related blocks all are green over the past 4 days.
Do a quick searching with https://search.apps.build01.ci.devcluster.openshift.com/?search=failed%3A.*works+for+CRD+with+validation+schema&maxAge=168h&context=2&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&wrap=on , there is no related errors for 4.4 over the past 7 days as well.
So the bug was fixed. move the bug verified.
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.