Uploaded image for project: 'OpenShift Windows Containers'
  1. OpenShift Windows Containers
  2. WINC-1188

Ensure CVP test operator-accidental-unpublishing-of-released-operators-bundle-image passes


    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • 3
    • False
    • None
    • False


      This test is currently failing and will block WMCO bundle builds April 1, 2024.
      The result of the test can be found in the CVP bundle build emails under
      `Detect Accidental Unpublishing of Released Operators Test (bundle-image)`

      Acceptance Criteria:

      • The CVP test passes for all supported release branches


      ---------- Forwarded message ---------
      From: Yash Nanavati <ynanavat@redhat.com>
      Date: Thu, Feb 29, 2024 at 1:35 AM
      Subject: [CVP Pipeline: Notification of change] Test modified and Apr 1, 2024 Gating Date: "Detect Accidental Unpublishing of Released Operators" - PLEASE READ!
      To: sp-cloud-announce <sp-cloud-announce@redhat.com>, container-factory-catalog <container-factory-catalog@redhat.com>, <openshift-pm@redhat.com>, operatorframework-pm <operatorframework-pm@redhat.com>, cp-devel <cp-devel@redhat.com>, cvp-users <cvp-users@redhat.com>, <exd-sp-releng@redhat.com>

      Hello all,

      On December 18, 2023, we added a new test to the CVP pipeline in the operator shipping workflow, which prevents accidental unpublishing of content. You can read the last communication highlighting the reason behind adding the test in the email with subject "[CVP Pipeline: Notification of change] Test being added to detect accidental unpublishing of released operators - PLEASE READ!"

      Our original plan was to make the test gating on February 14, 2024 but we had to push that date since we discovered yet another scenario in which the operator upgrade graph was getting pruned. The modified test will go live in CVP starting March 1, 2024 and will continue to remain non-gating until April 1, 2024

      What you need to do (Updated: Recent changes have been stated in bold letters): 

      Whenever you release an operator version with the “olm.skipRange” annotation, you should either add the “spec.replaces” property pointing to the previous latest release in the channel or mention every previously published bundle of the channels your release is targeting in "spec.skips". The only exception to this rule is if you are releasing the first version in a new channel.

      So far, there were no checks in the CVP pipeline to enforce this. Once released, software must remain available for users to install for the above reasons since many of our customers are only sometimes running the latest release of your product and are often also running in an internet-disconnected environment.

      What we are doing (Updated: Recent changes have been stated in bold letters):

      We are in the process of adding the modified check to the CVP pipeline. We plan to add non-blocking warnings when these checks start to detect the problematic metadata constellation described above that would lead to pruning, beginning on Friday, March 1, 2024.

      We plan to switch these checks to blocking on Monday, April 1, 2024.

      If you have any questions, please do not hesitate to open a Jira in the CVP Jira project

            Unassigned Unassigned
            rh-ee-ssoto Sebastian Soto
            0 Vote for this issue
            6 Start watching this issue