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

[4.15] Can't install operator on 4.15 after uninstalling it on a prior version

XMLWordPrintable

    • Important
    • No
    • Veritas OLM Sprint 256
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide

      * Previously, installing an Operator could sometimes fail if the same Operator had been previously installed and uninstalled. This was due to a caching issue. This bug fix updates {olm} to correctly install the Operator in this scenario, and as a result this issue no longer occurs.
      __________
      This change fixes an issue where operator bundle unpack jobs cannot be found by OLM when installing an operator if they had already been created. This fix prevents an issue where installing an operator in 4.14, uninstalling that operator, upgrading the cluster to 4.15 and the installing that operator could cause a failure without manually removing a job resource from OLM's install path.
      Show
      * Previously, installing an Operator could sometimes fail if the same Operator had been previously installed and uninstalled. This was due to a caching issue. This bug fix updates {olm} to correctly install the Operator in this scenario, and as a result this issue no longer occurs. __________ This change fixes an issue where operator bundle unpack jobs cannot be found by OLM when installing an operator if they had already been created. This fix prevents an issue where installing an operator in 4.14, uninstalling that operator, upgrading the cluster to 4.15 and the installing that operator could cause a failure without manually removing a job resource from OLM's install path.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-31073. The following is the description of the original issue:
      —
      Description of problem

      I had a version of MTC installed on my cluster when it was running a prior version. I had deleted it some time ago, long before upgrading to 4.15. I upgraded it to 4.15 and needed to reinstall to take a look at something, but found the operator would not install.

      I originally tried with 4.15.0, but on failure upgraded to 4.15.3 to see if it would resolve the issue, but it did no.

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

      $ oc version
Client Version: 4.15.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: 4.15.3
Kubernetes Version: v1.28.7+6e2789b

      How reproducible:

      Always as far as I can tell. I have at least two clusters where I was able to reproduce it.

      Steps to Reproduce:

          1. Install Migration Toolkit for Containers on OpenShift 4.14
    2. Uninstall it
    3. Upgrade to 4.15
    4. Try to install it again

      Actual results:

      The operator never installs. UI just shows "Upgrade status: Unkown Failure"

Observe the catalog operator logs and note errors like:
E0319 21:35:57.350591       1 queueinformer_operator.go:319] sync {"update" "openshift-migration"} failed: bundle unpacking failed with an error: [roles.rbac.authorization.k8s.io "c1572438804f004fb90b6768c203caad96c47331f7ecc4f68c3cf6b43b0acfd" already exists, roles.rbac.authorization.k8s.io "724788f6766aa5ba19b24ef4619b6a8e8e856b8b5fb96e1380f0d3f5b9dcb7a" already exists]

If you delete the roles, you'll get the same for rolebindings, then the same for jobs.batch, and then configmaps.

      Expected results:

      Operator just installs

      Additional info:

      If you clean up all these resources the operator will install successfully.

            rh-ee-dfranz Daniel Franz
            openshift-crt-jira-prow OpenShift Prow Bot
            Kui Wang Kui Wang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: