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

cluster operator node-tuning reported Progressing=True with reason=Reconciling for a node reboot

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.20
    • Node Tuning Operator
    • None
    • 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:

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

      Job example

      Sep 26 02:18:35.298 W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      Sep 26 02:18:35.298 - 142s  W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      Sep 26 02:25:17.149 W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      Sep 26 02:25:17.149 - 91s   W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      Sep 26 02:29:03.199 W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      Sep 26 02:29:03.199 - 51s   W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      Sep 26 02:32:28.465 W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      Sep 26 02:32:28.465 - 75s   W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      Sep 26 02:37:59.135 W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      Sep 26 02:37:59.135 - 58s   W clusteroperator/node-tuning condition/Progressing reason/Reconciling status/True Working towards "4.21.0-0.ci-2025-09-26-000607-test-ci-op-r6vphj1z-latest"
      {code:none}
      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

      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:

          

              team-nto Team NTO
              hongkliu Hongkai Liu
              None
              None
              Liquan Cui Liquan Cui
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: