Bug 1830093

Summary:	test: [sig-api-machinery] CustomResourcePublishOpenAPI [Couldn't find resource for "crd-publish-openapi..."
Product:	OpenShift Container Platform	Reporter:	Brett Tofel <btofel>
Component:	kube-apiserver	Assignee:	Lukasz Szaszkiewicz <lszaszki>
Status:	CLOSED ERRATA	QA Contact:	Ke Wang <kewang>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3.0	CC:	aos-bugs, lszaszki, mfojtik, xxia
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	4.3.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:	test: [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] [Top Level] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]
Last Closed:	2020-06-03 03:30:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1828790
Bug Blocks:

Description Brett Tofel 2020-04-30 20:04:13 UTC

test: [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] [Top Level] [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] failed, see job:

Can be seen flaking pretty frequently, as instance:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-disruptive-4.4/84

With text:

fail [k8s.io/kubernetes/test/e2e/apimachinery/crd_publish_openapi.go:119]: Apr 18 13:46:05.768: failed to explain e2e-test-crd-publish-openapi-1880-crds.spec: error running /usr/bin/kubectl --server=https://api.ci-op-d09mjmhk-16905.origin-ci-int-aws.dev.rhcloud.com:6443 --kubeconfig=/tmp/admin.kubeconfig explain e2e-test-crd-publish-openapi-1880-crds.spec:
Command stdout:

stderr:
error: Couldn't find resource for "crd-publish-openapi-test-foo.example.com/v1, Kind=E2e-test-crd-publish-openapi-1880-crd"

error:
exit status 1

Comment 1 Lukasz Szaszkiewicz 2020-05-20 08:36:35 UTC

This bug is actively worked on.

Comment 5 Ke Wang 2020-05-26 03:31:53 UTC

From https://testgrid.k8s.io/redhat-openshift-ocp-release-4.3-blocking#release-openshift-origin-installer-e2e-gcp-4.3&sort-by-flakiness view, searching the keywords '[sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD with validation schema' on page, we can see the related blocks all are green over the past 10 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.3 over the past 14 days as well.

So the bug was fixed. move the bug verified.

Comment 7 errata-xmlrpc 2020-06-03 03:30:45 UTC

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-2020:2256