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

Cluster Operator monitoring has not completed version change after 30 minutes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • 4.21
    • Monitoring
    • Quality / Stability / Reliability
    • False
    • Hide

      None

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

      Description of problem:

      A component in a cluster with less than 250 nodes must complete a version
      change within a limited period of time: 90 minutes for Machine Config Operator and 20 minutes for others.
      Failure jobs: example1 and example2.

          : [Monitor:cluster-version-checker][bz-Monitoring] clusteroperator/monitoring must complete version change within limited time expand_less3h31m40s{Cluster Operator monitoring has not completed version change after 30 minutes  Cluster Operator monitoring has not completed version change after 30 minutes}

      How reproducible:

      The regression shows up in component ready: periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-upgrade-fips.

      The upgrade is to 4.21.0-0.nightly-2025-11-07-015858 (from 4.21.0-0.nightly-2025-11-05-234508).

      None of the failing job completed, but it seems all blocked on monitoring.

              jfajersk@redhat.com Jan Fajerski
              hongkliu Hongkai Liu
              None
              None
              Junqi Zhao Junqi Zhao
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: