-
Bug
-
Resolution: Unresolved
-
Major
-
4.19, 4.20, 4.21
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
CLOUD Sprint 277
-
1
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-54703. The following is the description of the original issue:
—
Description of problem:
Create same name capi machine/awsmachine with mapi machine, set MAPI machine status.authoritativeAPI to ClusterAPI, but FailedToConvertCAPIMachineToMAPI, report error "unsupported owner kind for owner reference conversion", the capi machine is a standalone machine, it is not created by machineset, the owner kind is Cluster instead of Machineset.
Version-Release number of selected component (if applicable):
4.19.0-0.ci-2025-04-07-182331
How reproducible:
Always
Steps to Reproduce:
1. Create a mapi machine 2. Create a capi awsmachine and machine, same name with mapi machine 3. Set MAPI machine status.authoritativeAPI to ClusterAPI
Actual results:
FailedToConvertCAPIMachineToMAPI, unsupported owner kind for owner reference conversion status: addresses: - address: 10.0.1.101 type: InternalIP - address: ip-10-0-1-101.us-east-2.compute.internal type: InternalDNS - address: ip-10-0-1-101.us-east-2.compute.internal type: Hostname authoritativeAPI: ClusterAPI conditions: - lastTransitionTime: "2025-04-08T03:01:27Z" status: "True" type: Drainable - lastTransitionTime: "2025-04-08T03:02:00Z" status: "True" type: InstanceExists - lastTransitionTime: "2025-04-08T03:24:52Z" message: The AuthoritativeAPI is set to ClusterAPI reason: AuthoritativeAPINotMachineAPI status: "True" type: Paused - lastTransitionTime: "2025-04-08T03:24:52Z" message: unsupported owner kind for owner reference conversion reason: FailedToConvertCAPIMachineToMAPI severity: Error status: "False" type: Synchronized - lastTransitionTime: "2025-04-08T03:01:27Z" status: "True" type: Terminable lastUpdated: "2025-04-08T03:24:52Z" nodeRef: kind: Node name: ip-10-0-1-101.us-east-2.compute.internal uid: ca85ab5b-dd2a-4fb1-a116-502bce676930 phase: Running providerStatus: conditions: - lastTransitionTime: "2025-04-08T03:01:30Z" message: Machine successfully created reason: MachineCreationSucceeded status: "True" type: MachineCreation instanceId: i-0b2071c4a79fd8d04 instanceState: running synchronizedGeneration: 0 $ oc get machine -n openshift-cluster-api zhsun-aws48-444p5-test -o yaml apiVersion: cluster.x-k8s.io/v1beta1 kind: Machine metadata: creationTimestamp: "2025-04-08T03:04:57Z" finalizers: - machine.cluster.x-k8s.io generation: 2 labels: cluster.x-k8s.io/cluster-name: zhsun-aws48-444p5 machine.openshift.io/cluster-api-cluster: zhsun-aws48-444p5 node-role.kubernetes.io/infra: "" test: example name: zhsun-aws48-444p5-test namespace: openshift-cluster-api ownerReferences: - apiVersion: cluster.x-k8s.io/v1beta1 kind: Cluster name: zhsun-aws48-444p5 uid: 7bc5afc4-d5b3-4085-8e04-cce4381aaa5e resourceVersion: "95465" uid: c88f16e6-bc3f-46f5-ac37-dac4c8afb571 $ oc get machine -n openshift-cluster-api NAME CLUSTER NODENAME PROVIDERID PHASE AGE VERSION zhsun-aws48-444p5-test zhsun-aws48-444p5 ip-10-0-20-210.us-east-2.compute.internal aws:///us-east-2a/i-0bde9efa1a5f829ea Running 50m $ oc get awsmachine -n openshift-cluster-api NAME CLUSTER STATE READY INSTANCEID MACHINE zhsun-aws48-444p5-test zhsun-aws48-444p5 running true aws:///us-east-2a/i-0bde9efa1a5f829ea zhsun-aws48-444p5-test $ oc get machine.m -n openshift-machine-api NAME PHASE TYPE REGION ZONE AGE zhsun-aws48-444p5-master-0 Running m6i.xlarge us-east-2 us-east-2a 3h57m zhsun-aws48-444p5-master-1 Running m6i.xlarge us-east-2 us-east-2b 3h57m zhsun-aws48-444p5-master-2 Running m6i.xlarge us-east-2 us-east-2c 3h57m zhsun-aws48-444p5-test Running m6i.xlarge us-east-2 us-east-2a 53m
Expected results:
CAPI to MAPI Machine conversion succeed
Additional info:
- clones
-
OCPBUGS-54703 CAPI to MAPI Machine conversion failed
-
- Verified
-
- is blocked by
-
OCPBUGS-54703 CAPI to MAPI Machine conversion failed
-
- Verified
-
- links to