Bug 1781843 - error building openapi models for clusteroperators.config.openshift.io
Summary: error building openapi models for clusteroperators.config.openshift.io
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3.0
Assignee: Mike Dame
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On: 1781768
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-10 16:52 UTC by Mike Dame
Modified: 2020-01-23 11:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1781768
Environment:
Last Closed: 2020-01-23 11:18:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 24290 0 None closed [release-4.3] Bug 1781843: UPSTREAM: 85162: Strip nullable for server-side apply 2021-01-04 07:40:38 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:19:16 UTC

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


Note You need to log in before you can comment on or make changes to this bug.