Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3406

Restrict publishing DS 3.2 to only OCP 4.10 and 4.11 indexes

XMLWordPrintable

    • False
    • None
    • False
    • n/a
    • Not Required

      While we don't need DS 3.x on OCP 4.12 yet (as it won't be out until ~ DS 3.4), we're currently BUILDING IIBs for 4.10, 4.11, and 4.12RC.

      The result of this is an UNSTABLE build in CVP, due to this failure to resolve the upgrade tree.

      Build state history for v4.12:
      2022-09-30T01:04:40.967942Z - failed - Failed to add the bundles to the index image: Invalid bundle devspacesoperator.v3.2.0, replaces nonexistent bundle devspacesoperator.v3.1.0-0.1661879180.p
      2022-09-30T01:03:59.728777Z - in_progress - Checking if bundles are already present in index image
      2022-09-30T01:03:59.616172Z - in_progress - Building the index image for the following arches: amd64, s390x
      2022-09-30T01:03:55.999565Z - in_progress - Resolving the container images
      2022-09-30T01:03:55.540048Z - in_progress - Resolving the bundles
      2022-09-30T01:03:47.853190Z - in_progress - The request was initiated
      

      Failure in Greenwave (errata):

      Not sure the best solution here... we can STOP building for 4.12 by setting an upper limit for com.redhat.openshift.versions in dockerfile, but that only postpones the problem.

      Perhaps there's a way to remove the `replaces:` value in the CSV for a bundle build for 4.12+ ?

      We'd need two different operator-bundle:3.2-zzz builds to achieve that.

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: