Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1781843

Summary:	error building openapi models for clusteroperators.config.openshift.io
Product:	OpenShift Container Platform	Reporter:	Mike Dame <mdame>
Component:	kube-apiserver	Assignee:	Mike Dame <mdame>
Status:	CLOSED ERRATA	QA Contact:	Xingxing Xia <xxia>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3.0	CC:	aos-bugs, deads, mfojtik, nagrawal, xxia
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1781768	Environment:
Last Closed:	2020-01-23 11:18:54 UTC	Type:	---
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:	1781768
Bug Blocks:

Description Mike Dame 2019-12-10 16:52:23 UTC

+++ This bug was initially created as a clone of Bug #1781768 +++

Seeing

E1209 06:35:01.956334       1 customresource_handler.go:655] error building openapi models for clusteroperators.config.openshift.io: ERROR $root.definitions.io.openshift.config.v1.ClusterOperator.properties.status.properties.extension has invalid property: nullable

in kube-apiserver logs from https://storage.googleapis.com/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.3/453/artifacts/e2e-aws/pods/openshift-kube-apiserver_kube-apiserver-ip-10-0-143-43.ec2.internal_kube-apiserver-3.log in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.3/453 .  

I think this impacts explain output and may indicate that we have different definitions of the clusteroperator CRD fighting.

Comment 2 Xingxing Xia 2019-12-24 07:24:29 UTC

Verified in 4.3.0-0.nightly-2019-12-24-014531:
oc get crd -o yaml | grep nullable
Given CRDs have nullable property, KAS pod logs don't have above errors now.
Per the upstream k8s issue https://github.com/kubernetes/kubernetes/issues/85127 , everything kept working, thus lowering severity.
Reporting a separate bug 1786273 for another similar error.

Comment 4 errata-xmlrpc 2020-01-23 11:18:54 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:0062