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

Unable to Move to 4.20 Index Due to Missing Installable Content with Max OCP Version in 4.20 Catalog

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.20
    • 4.20
    • OLM
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Approved
    • Nidoran Sprint 274, Oddish Sprint 275
    • 2
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We need to bump the 4.20 catalogue images to support OLMv1.
      To do that, the pull request must pass CI: https://github.com/openshift/operator-framework-operator-controller/pull/393

      For us to make the test pass, we need to have:

      • An operator version that exists in both 4.19 and 4.20 catalogs
      • It must be installed successfully with OLMv1
      • It must have olm.maxOpenShiftVersion < 4.20

      This test checks that cluster upgrades are blocked when such an operator is installed.

      Problem: We don’t have any operator in the 4.20 catalog that meets all these conditions.
      That’s why can not change the test to use ANY, and we can’t move forward with the 4.20 bump. https://issues.redhat.com/browse/OCPBUGS-60154?focusedId=27733043&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27733043

      Impact: Blocks CI and prevents OLMv1 upgrade Catalog Sources indexes images from uses 4.20 tags. Consequently, it blocks the release

      Test Details:

       

              rh-ee-cmacedo Camila Macedo
              rh-ee-cmacedo Camila Macedo
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: