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

Consolidate updatingConfig/Version conditions control from CAPI controller with nodepool controller

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.19.0
    • 4.18.z
    • HyperShift
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • Hypershift Sprint 263
    • 1
    • Done
    • Bug Fix
    • Hide
      * Previously, both the `NodePool` controller and the cluster API controller set the `updatingConfig` status condition on the `NodePool` custom resource. As a consequence, the `updatingConfig` status was constantly changing. With this release, the logic to update the `updatingConfig` status is consolidated between the two controllers. As a result, the `updatingConfig` status is correctly set. (link:https://issues.redhat.com/browse/OCPBUGS-45322[OCPBUGS-45322])
      Show
      * Previously, both the `NodePool` controller and the cluster API controller set the `updatingConfig` status condition on the `NodePool` custom resource. As a consequence, the `updatingConfig` status was constantly changing. With this release, the logic to update the `updatingConfig` status is consolidated between the two controllers. As a result, the `updatingConfig` status is correctly set. (link: https://issues.redhat.com/browse/OCPBUGS-45322 [ OCPBUGS-45322 ])
    • None
    • None
    • None
    • None

      Description of problem:

          Currently both the nodepool controller and capi controller set the updatingConfig condition on nodepool upgrades. We should only use one to set the condition to avoid constant switching between conditions and to ensure the logic used for setting this condition is the same.

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

          4.18

      How reproducible:

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

          CAPI and Nodepool controller set a different status because their logic is not consistent.

      Expected results:

          CAPI and Nodepool controller set  the same status because their logic is not cosolidated.

      Additional info:

              pstefans@redhat.com Patryk Stefanski
              pstefans@redhat.com Patryk Stefanski
              None
              None
              Wen Wang Wen Wang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: