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

talm operator bundle ships with a "skipRange" annotation but without the "replaces" property (CSV)

XMLWordPrintable

    • Important
    • No
    • False
    • Hide

      None

      Show
      None

      If we release our newer operator version without the correct metadata, it will release that new version just fine but at the same time it will unpublish all earlier versions in the channel, making the new version effectively the only entry in that channel.

      This happens when a new operator bundle ships with a "skipRange" annotation but without the "replaces" property in the operators OLM metadata (CSV):
      talm CSV

      How to fix this ?

      We need start shipping out releases with the "replaces" property in addition to the "skipRange" property.|
      See all the details looking for "skipRange" in the section "Update Graph Gotchas":

      Best practices

      All talm releases are affected so this ocpbug must be backported properly.

       

              saskari@redhat.com Saeid Askari
              rauherna@redhat.com Raúl Hernández
              Joshua Clark Joshua Clark
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: