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

Sometime status.authoritativeAPI stuck in Migrating when changing AuthoritativeAPI from ClusterAPI to MachineAPI

XMLWordPrintable

    • Moderate
    • None
    • CLOUD Sprint 271, CLOUD Sprint 272
    • 2
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-56487. The following is the description of the original issue:

      Description of problem:

      MAPI machineset status.authoritativeAPI stuck in Migrating when changing AuthoritativeAPI from ClusterAPI to MachineAPI

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

      4.19.0-0.nightly-2025-05-19-005500  

      How reproducible:

      Met 3 times  

      Steps to Reproduce:

      1. Create a new mapi machineset with authoritativeAPI ClusterAPI    
      2. Change authoritativeAPI from ClusterAPI to MachineAPI 
      3. Check machineset status
          

      Actual results:

      MAPI machineset status.authoritativeAPI stuck in Migrating    
      
      $ oc get machineset.m machineset-auth-capi -o yaml          
      apiVersion: machine.openshift.io/v1beta1
      kind: MachineSet
      metadata:
        annotations:
          capacity.cluster-autoscaler.kubernetes.io/labels: kubernetes.io/arch=amd64
          machine.openshift.io/GPU: "0"
          machine.openshift.io/memoryMb: "16384"
          machine.openshift.io/vCPU: "4"
        creationTimestamp: "2025-05-20T10:21:34Z"
        generation: 5
        labels:
          machine.openshift.io/cluster-api-cluster: zhsunaws-vpkgb
          machine.openshift.io/cluster-api-machineset: zhsunaws-vpkgb-86afb
          machine.openshift.io/reason: actuator-e2e
        name: machineset-auth-capi
        namespace: openshift-machine-api
        resourceVersion: "339649"
        uid: 8b1e2013-84a4-4a95-b57d-b18d038a9b25
      spec:
        authoritativeAPI: MachineAPI
        deletePolicy: Oldest
        replicas: 1
        selector:
          matchLabels:
            machine.openshift.io/cluster-api-cluster: zhsunaws-vpkgb
            machine.openshift.io/cluster-api-machineset: zhsunaws-vpkgb-86afb
            machine.openshift.io/reason: actuator-e2e
        template:
          metadata:
            annotations:
              mapi-ano1: mapi-ano1
            labels:
              machine.openshift.io/cluster-api-cluster: zhsunaws-vpkgb
              machine.openshift.io/cluster-api-machineset: zhsunaws-vpkgb-86afb
              machine.openshift.io/reason: actuator-e2e
              mapi-label1: mapi-label1
          spec:
            authoritativeAPI: MachineAPI
      ...
      status:
        authoritativeAPI: Migrating
        conditions:
        - lastTransitionTime: "2025-05-20T10:25:45Z"
          message: The AuthoritativeAPI is set to Migrating
          reason: AuthoritativeAPINotMachineAPI
          status: "True"
          type: Paused
        - lastTransitionTime: "2025-05-20T10:25:45Z"
          message: 'failed to update MAPI machine set: Operation cannot be fulfilled on
            machinesets.machine.openshift.io "machineset-auth-capi": the object has been
            modified; please apply your changes to the latest version and try again'
          reason: FailedToUpdateMAPIMachineSet
          severity: Error
          status: "False"
          type: Synchronized
        observedGeneration: 5
        synchronizedGeneration: 3

      Expected results:

      MAPI machineset status.authoritativeAPI changed to MachineAPI

      Additional info:

      must-gather:

      https://drive.google.com/file/d/1aKIhXnllRCh_obTfP5R2stOKGdabS_KU/view?usp=sharing 

              ddonati@redhat.com Damiano Donati
              openshift-crt-jira-prow OpenShift Prow Bot
              Zhaohua Sun Zhaohua Sun
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: