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

cluster operator olm reported Progressing=True with reason=CatalogdDeploymentCatalogdControllerManager_Deploying or reason=OperatorcontrollerDeploymentOperatorControllerControllerManager_Deploying for a node reboot

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.20
    • OLM
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      co/olm reported Progressing=True only for a node reboot which should not happened during a normal cluster upgrade.

      Job example

      The example job does an upgrade from 4.20.0-0.ci-2025-09-23-172020 to 4.21.0-0.ci-2025-09-26-000607

      "message": {
                      "reason": "CatalogdDeploymentCatalogdControllerManager_Deploying",
                      "cause": "",
                      "humanMessage": "CatalogdDeploymentCatalogdControllerManagerProgressing: Waiting for Deployment to act on changes",
                      "annotations": {
                          "condition": "Progressing",
                          "reason": "CatalogdDeploymentCatalogdControllerManager_Deploying",
                          "status": "True"
                      }
                  }, 

      Another job example

      Oct 07 22:13:12.099 W clusteroperator/olm condition/Progressing reason/OperatorcontrollerDeploymentOperatorControllerControllerManager_Deploying status/True OperatorcontrollerDeploymentOperatorControllerControllerManagerProgressing: Waiting for Deployment to deploy pods
      Oct 07 22:13:12.099 - 39s   W clusteroperator/olm condition/Progressing reason/OperatorcontrollerDeploymentOperatorControllerControllerManager_Deploying status/True OperatorcontrollerDeploymentOperatorControllerControllerManagerProgressing: Waiting for Deployment to deploy pods
      
      2 unwelcome but acceptable clusteroperator state transitions while machine-config is progressing during the upgrade window from 2025-10-07T21:21:22Z to 2025-10-07T22:30:22Z.  These should not happen, but because they are tied to exceptions, the fact that they did happen is not sufficient to cause this test-case to fail:
      
      Oct 07 22:04:51.518 W clusteroperator/olm condition/Progressing reason/CatalogdDeploymentCatalogdControllerManager_Deploying status/True CatalogdDeploymentCatalogdControllerManagerProgressing: Waiting for Deployment to deploy pods (exception: https://issues.redhat.com/browse/OCPBUGS-62635)
      Oct 07 22:04:51.518 - 18s   W clusteroperator/olm condition/Progressing reason/CatalogdDeploymentCatalogdControllerManager_Deploying status/True CatalogdDeploymentCatalogdControllerManagerProgressing: Waiting for Deployment to deploy pods (exception: https://issues.redhat.com/browse/OCPBUGS-62635) 

      How reproducible:

      Seems always for 4.20 - 4.21 upgrades
      

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

      co does not go Progressing=True only for a node reboot

      Additional info:

          

              rh-ee-cchantse Catherine Chan-Tse
              hongkliu Hongkai Liu
              None
              None
              Jian Zhang Jian Zhang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: