-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.14
-> While upgrading the cluster from 4.13.38 -> 4.14.18, it is stuck on CCO, clusterversion is complaining about
"Working towards 4.14.18: 690 of 860 done (80% complete), waiting on cloud-credential".
While checking further we see that CCO deployment is yet to rollout.
-> ClusterOperator status.versions[name=operator] isn't a narrow "CCO Deployment is updated", it's "the CCO asserts the whole CC component is updated", which requires (among other things) a functional CCO Deployment. Seems like you don't have a functional CCO Deployment, because logs have it stuck talking about asking for a leader lease. You don't have Kube API audit logs to say if it's stuck generating the Lease request, or waiting for a response from the Kube API server.
- blocks
-
OCPBUGS-41233 Failed to list secrets when a large number exist on the cluster [4.17]
- Closed
- is cloned by
-
OCPBUGS-41233 Failed to list secrets when a large number exist on the cluster [4.17]
- Closed
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update