Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-28744

Upgrade blocked due to the OLM operator stuck in CrashLoopBackOff

    XMLWordPrintable

Details

    • Yes
    • Approved
    • False
    • Hide

      None

      Show
      None

    Description

      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:

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-29083 Upgrade blocked due to the OLM operator stuck in CrashLoopBackOff

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-29083 Upgrade blocked due to the OLM operator stuck in CrashLoopBackOff

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          links to

          Web Link must-gather

          GitHub openshift/operator-framework-olm#679: OCPBUGS-24587,OCPBUGS-28744: NO-ISSUE: Synchronize From Upstream Repositories

          GitHub openshift/operator-framework-olm#683: OCPBUGS-28744: * olm,catalog: only validate the resources we label

          GitHub operator-framework/operator-lifecycle-manager#3165: OCPBUGS-28744: olm,catalog: only validate the resources we label

          Web Link RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update

          Web Link Slack Thread

          Activity

            People

              skuznets@redhat.com Steve Kuznetsov
              zmird.openshift Zakaria Mird
              Jian Zhang Jian Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: