Cluster Operators degarded after the upgrade from 4.10 to 4.11 #1564
Replies: 3 comments 5 replies
-
Please attach (or upload to the public file sharing service) must-gather archive, even if its incomplete |
Beta Was this translation helpful? Give feedback.
-
Possibly a dupe of #1550? |
Beta Was this translation helpful? Give feedback.
-
@vrutkovs I have also encountered the same problem here during an OCP upgrade from 4.12.12 to 4.12.13:
This is a SNO cluster with OVNKubernetes instead of OpenShiftSDN. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
During the OKD upgrade from 4.10 --> 4.11, as soon as the MachineConfig operator started upgrading and started applying the upgrade on the master node, the console operator, authentication operator, openshift-apiserver operator etc. went down and even when all the nodes got upgraded and rebooted with the kubelet version (v1.24.6), the operators stayed downgraded et giving the errors like
APIServicesAvailable: "project.openshift.io.v1" is not ready: an attempt failed with statusCode = 503
APIServicesAvailable: "oauth.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Version
4.11.0-0.okd-2022-12-02-145640
Using Openshift SDN
UPI install method on Bare Metal servers (running on VMware Vsphere) hosted on OVH
ESXi 6.7 and later (VM version 14)
How reproducible
Upgrade the OKD cluster (Openshift SDN) from 4.10.0-0.okd-2022-07-09-073606 to 4.11.0-0.okd-2022-12-02-145640
Log bundle
Beta Was this translation helpful? Give feedback.
All reactions