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

CAPI AWSMachine status not converted to MAPI Machine providerStatus

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Low
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      When a MAPI Machine has spec.authoritativeAPI: ClusterAPI, the CAPI AWSMachine status should be converted to the MAPI Machine's status.providerStatus. However, the conversion is not working. 

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

      4.22.0-0.nightly-2025-12-22-044720

      How reproducible:

      always

      Steps to Reproduce:

      1. Create a MAPI Machine with spec.authoritativeAPI: ClusterAPI
      
      2. Wait for the machine to become Running
      
      3. Check the CAPI AWSMachine status - it has status.instanceState: running
      $ oc get awsmachine -n openshift-cluster-api zhsunaws22-m9hx6-worker-us-east-2a-capi -o yaml
      status:
        addresses:
        - address: ip-10-0-26-102.us-east-2.compute.internal
          type: InternalDNS
        - address: 10.0.26.102
          type: InternalIP
        conditions:
        - lastTransitionTime: "2025-12-22T12:20:38Z"
          status: "True"
          type: Ready
        - lastTransitionTime: "2025-12-22T12:20:38Z"
          status: "True"
          type: InstanceReady
        - lastTransitionTime: "2025-12-22T12:20:03Z"
          reason: NotPaused
          status: "False"
          type: Paused
        - lastTransitionTime: "2025-12-22T12:20:07Z"
          status: "True"
          type: SecurityGroupsReady
        instanceState: running
        ready: true
      
      4. Check the MAPI Machine status.providerStatus - it remains empty {}
      $ oc get machine.m zhsunaws22-m9hx6-worker-us-east-2a-capi -o yaml
      status:
        addresses:
        - address: ip-10-0-26-102.us-east-2.compute.internal
          type: InternalDNS
        - address: 10.0.26.102
          type: InternalIP
        authoritativeAPI: ClusterAPI
        conditions:
        - lastTransitionTime: "2025-12-22T12:20:03Z"
          status: "True"
          type: Drainable
        - lastTransitionTime: "2025-12-22T12:20:03Z"
          message: The AuthoritativeAPI status is set to 'ClusterAPI'
          reason: AuthoritativeAPINotMachineAPI
          status: "True"
          type: Paused
        - lastTransitionTime: "2025-12-22T12:20:03Z"
          status: "True"
          type: Terminable
        - lastTransitionTime: "2025-12-22T14:48:27Z"
          message: Successfully synchronized CAPI Machine to MAPI
          reason: ResourceSynchronized
          severity: ""
          status: "True"
          type: Synchronized
        lastUpdated: "2025-12-22T12:24:15Z"
        nodeRef:
          apiVersion: v1
          kind: Node
          name: ip-10-0-26-102.us-east-2.compute.internal
        phase: Running
        providerStatus: {}
        synchronizedGeneration: 2

      Actual results:

      The MAPI Machine's status.providerStatus is empty:
      status:
        providerStatus: {}

      Expected results:

      The MAPI Machine's status.providerStatus shouldn't be empty

      Additional info:

      must-gather: https://drive.google.com/file/d/1n2rq7PJ1gVkHV8cBbeJ2LMHX98ghlpOq/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:
              2 Start watching this issue

                Created:
                Updated: