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

Reinstalling an Operator sometimes fails, referencing nonexistent CSV

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Normal Normal
    • None
    • 4.12.0
    • OLM
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Sometimes, when uninstalling and re-installing an operator (due to different upgrade issue), the installation fails, with the subscription getting a condition that references nonexistent CSVs as causing a problem.
      
      In the example below, web terminal operator (v1.6.0) was uninstalled after a failed upgrade to v1.7.0 (due to another strange issue). When subscription is created again, no startingCSV is set so OLM should be trying to install v1.7.0.
      
      The subscription gets conditions like
          - lastTransitionTime: '2023-03-09T19:12:20Z'
            message: all available catalogsources are healthy
            reason: AllCatalogSourcesHealthy
            status: 'False'
            type: CatalogSourcesUnhealthy
          - message: >-
              constraints not satisfiable: clusterserviceversion web-terminal.v1.6.0
              exists and is not referenced by a subscription,
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.5.0-0.1657220207.p,
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.2.1,
              @existing/crw//web-terminal.v1.6.0,
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.6.0,
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.3.0,
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.7.0 and
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.4.0
              originate from package web-terminal, bundle
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.2.1 is
              deprecated, subscription web-terminal requires at least one of
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.7.0,
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.6.0,
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.5.0-0.1657220207.p,
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.4.0,
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.3.0 or
              redhat-operators/openshift-marketplace/fast/web-terminal.v1.2.1,
              subscription web-terminal exists
            reason: ConstraintsNotSatisfiable
            status: 'True'
            type: ResolutionFailed
      
      (note the ResolutionFailed condition reorders frequently and randomly)
      
      The message in the condition suggests that an existing CSV is the issue
      
      > clusterserviceversion web-terminal.v1.6.0 exists and is not referenced by a subscription
      
      However, no such CSV exists in the installation namespace.
      
      

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

      4.12.0
      

      How reproducible:

      Occasionally; randomly.
      

      Steps to Reproduce:

      1. Uninstall an operator via the OpenShift UI
      2. Create a new subscription for the Operator
      

      Actual results:

      Subscription fails to resolve operator
      

      Expected results:

      Install should succeed, or at least mention what the actual issue is.
      

      Additional info:

      Encountered a number of times over the last few months in Developer Sandbox clusters.
      
      Workaround:
      * Restart catalog-operator pod in openshift-operator-lifecycle-manager namespace (delete running pod and let it be recreated)
      * Delete failed subscription and re-create it
      

            agreene1991 Alexander Greene
            amisevsk Angel Misevski
            Kui Wang Kui Wang
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: