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

Sometimes mapi machine stuck in Provisioning when authoritativeAPI is ClusterAPI

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Low
    • None
    • None
    • None
    • CLOUD Sprint 272, CLOUD Sprint 273
    • 2
    • Done
    • Bug Fix
    • Hide
      * Before this update, the Machine API Operator attempted to reconcile `Machine` resources on platforms other than {aws-short} where the `.status.authoritativeAPI` field was not populated.
      As a consequence, compute machines remained in the `Provisioning` state indefinitely and never became operational.
      With this release, the Machine API Operator now populates the empty `.status.authoritativeAPI` field with the corresponding value in the machine specification.
      A guard is also added to the controllers to handle cases where this field might still be empty.
      As a result, `Machine` and `MachineSet` resources are reconciled properly and compute machines no longer remain in the `Provisioning` state indefinitely.
      (link:https://issues.redhat.com/browse/OCPBUGS-56849[OCPBUGS-56849])
      Show
      * Before this update, the Machine API Operator attempted to reconcile `Machine` resources on platforms other than {aws-short} where the `.status.authoritativeAPI` field was not populated. As a consequence, compute machines remained in the `Provisioning` state indefinitely and never became operational. With this release, the Machine API Operator now populates the empty `.status.authoritativeAPI` field with the corresponding value in the machine specification. A guard is also added to the controllers to handle cases where this field might still be empty. As a result, `Machine` and `MachineSet` resources are reconciled properly and compute machines no longer remain in the `Provisioning` state indefinitely. (link: https://issues.redhat.com/browse/OCPBUGS-56849 [ OCPBUGS-56849 ])
    • None
    • None
    • None
    • None

      Description of problem:

      Sometimes mapi machine stuck in Provisioning when authoritativeAPI is ClusterAPI, in most cases this phase is ""

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

      4.20.0-0.nightly-2025-05-28-190420

      How reproducible:

      Sometimes

      Steps to Reproduce:

      1. Create a new mapi machineset with authoritativeAPI:ClusterAPI
2. Check mapi machine phase
3.

      Actual results:

      mapi machine zhsunaws20-tkx5x-capi2-c7flr phase is Provisioning, in most cases it is like zhsunaws20-tkx5x-capi1-82ptf, phase is empty.

$ oc get machines.m       
NAME                                       PHASE          TYPE         REGION      ZONE         AGE
zhsunaws20-tkx5x-capi1-82ptf                                                                    24m
zhsunaws20-tkx5x-capi2-c7flr               Provisioning                                         25m
zhsunaws20-tkx5x-master-0                  Running        m6i.xlarge   us-east-2   us-east-2a   8h
zhsunaws20-tkx5x-master-1                  Running        m6i.xlarge   us-east-2   us-east-2b   8h
zhsunaws20-tkx5x-master-2                  Running        m6i.xlarge   us-east-2   us-east-2c   8h
zhsunaws20-tkx5x-worker-us-east-2a-prn8c   Running        m6i.xlarge   us-east-2   us-east-2a   8h
zhsunaws20-tkx5x-worker-us-east-2b-qhsbb   Running        m6i.xlarge   us-east-2   us-east-2b   7h46m
zhsunaws20-tkx5x-worker-us-east-2c-djzkd   Running        m6i.xlarge   us-east-2   us-east-2c   8h

zhsun:aws1/ $ oc get machines.cluster.x-k8s.io -n openshift-cluster-api                                                                                         [18:00:28]
NAME                                       CLUSTER            NODENAME                                    PROVIDERID                              PHASE     AGE     VERSION
zhsunaws20-tkx5x-capi1-82ptf               zhsunaws20-tkx5x   ip-10-0-77-74.us-east-2.compute.internal    aws:///us-east-2c/i-0532415adbbb918b7   Running   30m
zhsunaws20-tkx5x-capi2-c7flr               zhsunaws20-tkx5x   ip-10-0-71-226.us-east-2.compute.internal   aws:///us-east-2c/i-01d5f640b88d8ba76   Running   30m
zhsunaws20-tkx5x-worker-us-east-2a-prn8c   zhsunaws20-tkx5x                                               aws:///us-east-2a/i-0763ec39b4b27c2da             8h
zhsunaws20-tkx5x-worker-us-east-2b-qhsbb   zhsunaws20-tkx5x                                               aws:///us-east-2b/i-062b3db011c75ccbd             7h51m
zhsunaws20-tkx5x-worker-us-east-2c-djzkd   zhsunaws20-tkx5x                                               aws:///us-east-2c/i-01c92416ae9db4c0a             8h

      Expected results:

      Mapi machine phase is empty when create mapi machineset with authoritativeAPI:ClusterAPI

      Additional info:

      must-gather: https://drive.google.com/file/d/13GxwpCii5WVM7YLuhrhnWxGa31gWbisG/view?usp=sharing

              ddonati@redhat.com Damiano Donati
              rhn-support-zhsun Zhaohua Sun
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: