This is a clone of issue OCPBUGS-28744. The following is the description of the original issue:
—
Description of problem:
$ oc adm upgrade info: An upgrade is in progress. Working towards 4.15.0-rc.4: 701 of 873 done (80% complete), waiting on operator-lifecycle-manager Upstream: https://api.openshift.com/api/upgrades_info/v1/graph Channel: candidate-4.15 (available channels: candidate-4.15, candidate-4.16) No updates available. You may still upgrade to a specific release image with --to-image or wait for new updates to be available. $ oc get pods -n openshift-operator-lifecycle-manager NAME READY STATUS RESTARTS AGE catalog-operator-db86b7466-gdp4g 1/1 Running 0 9h collect-profiles-28443465-9zzbk 0/1 Completed 0 34m collect-profiles-28443480-kkgtk 0/1 Completed 0 19m collect-profiles-28443495-shvs7 0/1 Completed 0 4m10s olm-operator-56cb759d88-q2gr7 0/1 CrashLoopBackOff 8 (3m27s ago) 20m package-server-manager-7cf46947f6-sgnlk 2/2 Running 0 9h packageserver-7b795b79f-thxfw 1/1 Running 1 14d packageserver-7b795b79f-w49jj 1/1 Running 0 4d17h
Version-Release number of selected component (if applicable):
How reproducible:
Unknown
Steps to Reproduce:
Upgrade from 4.15.0-rc.2 to 4.15.0-rc.4
Actual results:
The upgrade is unable to proceed
Expected results:
The upgrade can proceed
Additional info:
- clones
-
OCPBUGS-28744 Upgrade blocked due to the OLM operator stuck in CrashLoopBackOff
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHSA-2023:7198
OpenShift Container Platform 4.15 security update
