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

Cluster Operator olm did not report Progressing=True during a cluster update

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • 1
    • None
    • None
    • Rejected
    • Yanma Sprint 285
    • 1
    • In Progress
    • Bug Fix
    • Hide
      The cluster-olm-operator did not detect version changes during cluster upgrades. The operator failed to report Progressing=True status during upgrades, preventing accurate upgrade monitoring.

       **Fix**: Added version detection logic that compares RELEASE_VERSION against the stored operator version and sets Progressing=True when an upgrade is detected.
        **Result**: The operator now correctly reports Progressing status during upgrades, improving upgrade observability.
      Show
      The cluster-olm-operator did not detect version changes during cluster upgrades. The operator failed to report Progressing=True status during upgrades, preventing accurate upgrade monitoring.  **Fix**: Added version detection logic that compares RELEASE_VERSION against the stored operator version and sets Progressing=True when an upgrade is detected.   **Result**: The operator now correctly reports Progressing status during upgrades, improving upgrade observability.
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-65623. The following is the description of the original issue:
      —
      Description of problem:

      During Upgrade: The operator MUST report Progressing=True (since a version change is a configuration change). It is defined in the o/api docs.

      However, CO/olm did not in these upgrade jobs: example1(periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node).

      : [Monitor:legacy-cvo-invariants][bz-OLM] clusteroperator/olm must go Progressing=True during an upgrade test expand_less33m45s{  clusteroperator/olm was never Progressing=True during the upgrade window from 2025-11-14T06:20:08Z to 2025-11-14T06:53:53Z and CVO waited for it over 2 minutes from 2025-11-14T06:33:02Z to 2025-11-14T06:35:47Z}

      Version-Release number of selected component (if applicable):

      The job upgrades a cluster to 4.21.0-0.nightly-2025-11-14-050926 (from 4.21.0-0.nightly-2025-11-13-042845).

      How reproducible:

      Seems quite often for patch level updates in the aggregate job: aggregated-aws-ovn-single-node-upgrade-4.21-micro-release-openshift-release-analysis-aggregator.

       

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

              rashmigottipati Rashmi Gottipati
              hongkliu Hongkai Liu
              Jian Zhang Jian Zhang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: