Uploaded image for project: 'Operator Runtime'
  1. Operator Runtime
  2. OPRUN-4422

(OLMv1) QA: Validate upgrade (4.21 -> 4.22) for Marketplace-installed operators

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None

      We will remove the Marketplace index in 4.22. We need QA coverage to ensure operators installed from Marketplace on 4.21 keep working after upgrading the cluster to 4.22.

      Scope:

      • Cover both OLMv0 and OLMv1 installation paths.
      • Validate upgrade path from 4.21 to 4.22 where Marketplace index is removed.

      Acceptance Criteria:
      1) On OpenShift 4.21, install an operator from Marketplace using OLMv0.
      2) Upgrade the cluster to 4.22 (Marketplace index removed).
      3) Operator continues to reconcile successfully after upgrade
      4) Basic health checks pass (operator pods running, managed workload healthy).

      Notes :
      We are looking for a solution to warning/blocker upgrade when the users has operators installed from marketplace in 4.21 ( not sure if we will be able to do so https://issues.redhat.com/browse/OPRUN-4418 ) If so, we will need to either to check its behaviour. 

              Unassigned Unassigned
              rh-ee-cmacedo Camila Macedo
              None
              bruno andrade bruno andrade
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: