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

Installed Operators in "Failed" status after upgrading to 4.15.3

XMLWordPrintable

    • Critical
    • Yes
    • Phlogiston 250, Quality OLM Sprint 251
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      We upgraded our OpenShift Cluster from 4.4.16 to 4.15.3 and multiple operators are now in "Failed" status with the following CSV conditions such as:
      - NeedsReinstall installing: deployment changed old hash=5f6b8fc6f7, new hash=5hFv6Gemy1Zri3J9ulXfjG9qOzoFL8FMsLNcLR
      - InstallComponentFailed install strategy failed: rolebindings.rbac.authorization.k8s.io "openshift-gitops-operator-controller-manager-service-auth-reader" already exists
      
      All other failures refer to a similar "auth-reader" rolebinding that already exist.
       
          

      Version-Release number of selected component (if applicable):

      OpenShift 4.15.3
          

      How reproducible:

      Happened on several installed operators but on the only cluster we upgraded (our staging cluster)
          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

      
          

      Expected results:

      All operators should be up-to-date
          

      Additional info:

      
      This may be related to https://github.com/operator-framework/operator-lifecycle-manager/pull/3159 
          

            rh-ee-dfranz Daniel Franz
            xcoulon@redhat.com Xavier Coulon
            Kui Wang Kui Wang
            Votes:
            0 Vote for this issue
            Watchers:
            24 Start watching this issue

              Created:
              Updated:
              Resolved: