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

operator-metadata bundle cannot declare incompatibility with v4.7 (commas not allowed)

XMLWordPrintable

    • False
    • False
    • Undefined

      So, I tried to use "v4.6,v4.8" to say that CRW 2.11 is only compatible with OCP 4.6 and 4.8, but alas, CVP tests failed with this surprisingly detailed explanation:

      Please follow the information provided below about defining the OCP versions:
      
      
      Semantics
      
      1. We use a single version to mean a minimum of this version but will be automatically opted-in to the next version
      2. ‘=’ means a particular version ONLY
      3. A range to be used with deprecation to stop shipping updates to (in the case below) 4.8.
      
      |---            |---       |---          |---          |---          |---         |
      |               |"v4.5"    |"v4.6"       |"=v4.6"      |"v4.5-v4.7"  |"v4.5,v4.6" |
      |4.5 Index      |Included  |Not Included |Not Included |Included     |Included    |
      |4.6 Index      |Included  |Included     |Included     |Included     |Included    |
      |4.7 Stage Index|Included  |Included     |Not Included |Included     |Included    |
      |4.7 Index      |Included  |Included     |Not included |included     |Included    |
      |4.8 Stage Index|Included  |Included     |Not Included |Not Included |Included    |
      
      4. If the bundle has been deprecated in the vN index image, it will not be included in the vN index and subsequent versions.
      5. Commas are generally not allowed, and should not be used. For historical reasons, there are two special values that are currently allowed to contain commas, "v4.5,v4.6" and "v4.6,v4.5".
      Both behave as just "v4.5". The operator is supported on the v4.5 version of OpenShift or later.
      Any other usage of commas, e.g. "v4.6,v4.7", will prevent the operator from being added to the catalog.

      So, therefore, we can't exclude 2.11 from being included in the OCP 4.7 operatorhub IIB index.

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

              Created:
              Updated:
              Resolved: