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

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

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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/baremetal did not in these upgrade jobs: example1 and example2 and example3.

       : [Monitor:legacy-cvo-invariants][bz-Bare Metal Hardware Provisioning] clusteroperator/baremetal must go Progressing=True during an upgrade test expand_less1h0m35s{  clusteroperator/baremetal was never Progressing=True during the upgrade window from 2025-11-26T17:12:47Z to 2025-11-26T18:13:22Z and CVO waited for it over 2 minutes from 2025-11-26T17:34:38Z to 2025-11-26T18:07:31Z}

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

      The job upgrades a cluster to 4.21.0-0.ci-2025-11-26-155308 (from 4.21.0-0.ci-2025-11-26-030640).

      How reproducible:

          Seems quite often in periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-upgrade

              rhn-engineering-hpokorny Honza Pokorny
              hongkliu Hongkai Liu
              None
              None
              Jad Haj Yahya Jad Haj Yahya
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: