Job:
#OCPBUGS-33018issue7 days agoThe MCD can exit(255) during an upgrade and and degrade on content mismatch ON_QA
- [sig-cluster-lifecycle] Cluster completes upgrade
- [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial]
#OCPBUGS-23538issue3 months agoUpgrade got stuck for OLM catalog/olm operator pods keep CrashLoopBackOff CLOSED
Issue 15634738: Upgrade got stuck for OLM catalog/olm operator pods keep CrashLoopBackOff
Description: Description of problem:
 {code:none}
 CX has a cluster that was upgrading from 4.14.1 to 4.15.0-ec.2{code}
 Version-Release number of selected component (if applicable):
 {code:none}
  {code}
 How reproducible:
 {code:none}
 Upgrade cluster {code}
 Steps to Reproduce:
 {code:none}
 1. Upgrade the cluster and set the version to 4.15.0-ec.2 from 4.14.1
 {code}
 Actual results:
 {code:none}
 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{code}
 Expected results:
 {code:none}
 OLM operators should be in running status{code}
 Additional info:
 {code:none}
  {code}
 
 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]
Status: CLOSED

Found in 0.00% of runs (0.00% of failures) across 1 total runs and 1 jobs (100.00% failed) in 83ms - clear search | chart view - source code located on github