Also hit in 4.3 env of payload 4.3.0-0.nightly-2019-12-24-014531. The difference is, 4.3 KAS pod logs only show one line of such error, no other lines of the error for other CRDs: E1224 02:31:52.461037 1 customresource_handler.go:655] error building openapi models for clusterresourcequotas.quota.openshift.io: ERROR $root.definitions.io.openshift.quota.v1.ClusterResourceQuota.properties.spec.properties.quota.properties.hard.additionalProperties.schema has invalid property: anyOf +++ This bug was initially created as a clone of Bug #1786269 +++ Description of problem: KAS pod logs show "error building openapi models ... has invalid property: anyOf" for CRDs. This is found in 4.3/4.4 when verifying bug 1781843. Version-Release number of selected component (if applicable): 4.4.0-0.nightly-2019-12-20-210709
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing severity from "medium" to "low". If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This is just noise without consequence. Google engineers are fixing this, hopefully ready in 1.19 with 4.6.
Reconsidering in 4.6 after 1.19 rebase.
Still waiting for 1.19 rebase.
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
Removing LifecycleStale as per previous comments.
In 4.7 the earliest. Marking with UpcomingSprint.
Hi, I have similar problem to this bug (on GCP): error building openapi models for machinehealthchecks.machine.openshift.io: ERROR $root.definitions.io.openshift.machine.v1beta1.MachineHealthCheck.properties.spec.properties.maxUnhealthy has invalid property: anyOf Since this bug is effectively blocking any installation, it should have priority much higher than low. Thanks
> Since this bug is effectively blocking any installation, it should have priority much higher than low. This does not block any installation. It's noise without consequences.
This is still an issue. Waiting for upstream to fix it.
Should be fixed through https://github.com/kubernetes/kubernetes/pull/97172 in 4.8.
The LifecycleStale keyword was removed because the bug moved to QE. The bug assignee was notified.
Verification steps: $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-05-19-123944 True False 93m Cluster version is 4.8.0-0.nightly-2021-05-19-123944 $ oc get po -n openshift-kube-apiserver -l apiserver NAME READY STATUS RESTARTS AGE kube-apiserver-ip-10-0-154-205.us-east-2.compute.internal 5/5 Running 0 95m kube-apiserver-ip-10-0-172-127.us-east-2.compute.internal 5/5 Running 0 101m kube-apiserver-ip-10-0-200-136.us-east-2.compute.internal 5/5 Running 0 104m $ oc logs kube-apiserver-ip-10-0-154-205.us-east-2.compute.internal -n openshift-kube-apiserver | grep 'error building' Using deprecated annotation `kubectl.kubernetes.io/default-logs-container` in pod/kube-apiserver-ip-10-0-154-205.us-east-2.compute.internal. Please use `kubectl.kubernetes.io/default-container` instead No results found.
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. https://access.redhat.com/errata/RHSA-2021:2438