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

CAPI MachineSet should be created unpaused when it is authoritative

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • No
    • None
    • CLOUD Sprint 271
    • 1
    • Done
    • Bug Fix
    • Hide
      * Before this update, on clusters that support migrating Machine API resources to Cluster API resources, the {cluster-capi-operator} could create an authoritative Cluster API compute machine set in the `Paused` state.
      As a consequence, the newly created Cluster API compute machine set could not reconcile or scale machines even though it was using the authoritative API.
      With this release, the Operator now ensures that Cluster API compute machine sets are created in an unpaused state when the Cluster API is authoritative.
      As a result, newly created Cluster API compute machine set are reconciled immediately and normal scaling and machine lifecycle operations proceed as intended when the Cluster API is authoritative.
      (link:https://issues.redhat.com/browse/OCPBUGS-56604[OCPBUGS-56604])
      Show
      * Before this update, on clusters that support migrating Machine API resources to Cluster API resources, the {cluster-capi-operator} could create an authoritative Cluster API compute machine set in the `Paused` state. As a consequence, the newly created Cluster API compute machine set could not reconcile or scale machines even though it was using the authoritative API. With this release, the Operator now ensures that Cluster API compute machine sets are created in an unpaused state when the Cluster API is authoritative. As a result, newly created Cluster API compute machine set are reconciled immediately and normal scaling and machine lifecycle operations proceed as intended when the Cluster API is authoritative. (link: https://issues.redhat.com/browse/OCPBUGS-56604 [ OCPBUGS-56604 ])
    • None
    • None
    • None
    • None

      Description of problem:

          When a MAPI MachineSet is created with .spec.authoritativeAPI: ClusterAPI, the authoritative CAPI MachineSet mirror is created as paused.

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

      How reproducible:

          Always

      Steps to Reproduce:

          1. Create a MAPI MachineSet is created with .spec.authoritativeAPI: ClusterAPI
    2. Check the paused condition in the status of the mirror CAPI MachineSet
    3.

      Actual results:

          the authoritative CAPI MachineSet mirror is created as paused

      Expected results:

          the authoritative CAPI MachineSet mirror should not be paused

      Additional info:

          We fixed a couple of similar bugs on the machine sync controller here: OCPBUGS-54970 OCPBUGS-56604

              ddonati@redhat.com Damiano Donati
              ddonati@redhat.com Damiano Donati
              None
              None
              Huali Liu Huali Liu
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: