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

Fix race condition in Helm to Boxcutter migration during OLM upgrades

XMLWordPrintable

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

      None

      Show
      None
    • False
    • 3
    • None
    • None
    • Weedle Sprint 283

      When upgrading OLM from standard (Helm runtime) to experimental (Boxcutter runtime), the BoxcutterStorageMigrator creates a ClusterExtensionRevision from the existing Helm release. However, the migrated revision was created without status conditions, causing a race condition where it wasn't recognized as "Installed".

      Real-World Scenario

      What We're Doing

      Day 1: You install OLM standard edition and install PostgreSQL operator v2.0.0

      • Everything works great ✅
      • Your databases are running ✅

      Day 2: You want to try the new Boxcutter runtime (experimental features)

      • You upgrade OLM from standard to experimental
      • OLM upgrade completes successfully ✅
      • PostgreSQL still runs fine ✅

      Day 3: PostgreSQL v2.1.0 is released with bug fixes you need

      • We try to upgrade PostgreSQL from v2.0.0 → v2.1.0
      • It FAILS ❌
      • Error: "Cannot determine installed version"
      • You're stuck on old version with bugs ❌

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

                Created:
                Updated:
                Resolved: