Upgrade from 4.17 to 4.18 failing as not generated the job in RHOCP 4
Issue
- The upgrade from OpenShift 4.17 to 4.18 does not start
-
When it's launched the upgrade from 4.17 to 4.18, the job in the
openshift-cluster-versionnamespace is not able to be completed:$ oc get jobs -n openshift-cluster-version NAME STATUS COMPLETIONS DURATION AGE version-4.18.30-ghz4b Running 0/1 17m -
The pod for the job in the
openshift-cluster-versionis not started and it is innot ready, continuing to wait:2026-01-28T23:31:01.858406906Z I0128 23:31:01.858075 1 batch.go:29] Job version-4.18.30-ghz4b in namespace openshift-cluster-version is not ready, continuing to wait. 2026-01-28T23:31:04.717315660Z I0128 23:31:04.717262 1 batch.go:55] No active pods for job version-4.18.30-ghz4b in namespace openshift-cluster-version 2026-01-28T23:31:04.717315660Z I0128 23:31:04.717294 1 batch.go:29] Job version-4.18.30-ghz4b in namespace openshift-cluster-version is not ready, continuing to wait. 2026-01-28T23:31:07.711490941Z I0128 23:31:07.711442 1 batch.go:55] No active pods for job version-4.18.30-ghz4b in namespace openshift-cluster-version 2026-01-28T23:31:07.711490941Z I0128 23:31:07.711468 1 batch.go:29] Job version-4.18.30-ghz4b in namespace openshift-cluster-version is not ready, continuing to wait.
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4.17
- 4.18
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.