Major Description of problem:
CX has a cluster that was upgrading from 4.14.1 to 4.15.0-ec.2
Version-Release number of selected component (if applicable):
How reproducible:
Upgrade cluster
Steps to Reproduce:
1. Upgrade the cluster and set the version to 4.15.0-ec.2 from 4.14.1
Actual results:
Upgrade got stuck from OLM operators kept CrashLoopBackOff oc get pods -n openshift-operator-lifecycle-manager NAME READY STATUS RESTARTS AGE catalog-operator-6b487fc45d-szbbz 0/1 CrashLoopBackOff 34 (97s ago) 164m collect-profiles-28343445-4mw29 0/1 Completed 0 46m collect-profiles-28343460-9pf82 0/1 Completed 0 31m collect-profiles-28343475-kszxh 0/1 Completed 0 16m collect-profiles-28343490-dn44t 1/1 Running 0 82s olm-operator-869c4ffcb9-4mzdz 0/1 CrashLoopBackOff 35 (4m19s ago) 161m package-server-manager-648f6cd4f-7txqk 2/2 Running 0 3h23m packageserver-f7b74f575-7p9bs 1/1 Running 0 6d1h packageserver-f7b74f575-pdtqj 1/1 Running 0 3h23m
Expected results:
OLM operators should be in running status
Additional info:
This issue shows up as a Cluster Version Operator component readiness regression due to failing the following tests:
- [sig-cluster-lifecycle] Cluster completes upgrade
- [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial]
- relates to
-
OCPBUGS-23514 Upgrade from 4.14.1 to 4.15.0-ec.2 is stuck but not reported as such by CVO
-
- New
-
- links to
-
RHEA-2024:0041
OpenShift Container Platform 4.16.z bug fix update
