-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.19.z
-
Quality / Stability / Reliability
-
False
-
-
3
-
Important
-
None
-
x86_64
-
Production
-
None
-
None
-
None
-
Metal Platform 276
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description:
Adding a bare metal worker to an existing cluster creates the node without bmh resource. node Followed kcs link https://access.redhat.com/solutions/6471021 but The yaml shows the node as discovered and poweredOn: False (the node was powered on).
This was attempted, the behavior is adding the BMH resource, says discovered but powered on false, adding in the machine after associating with the node, the machine is automatically deleted, the machine set is deleting the machine prior to allowing it, if you add the BMH resource, link to node and turn up the machineset by 1, it fails, the node must be removed and allowed to come back into the cluser.
Version: 4.18/4.19
How reproducable: happens every time
Steps to reproduce
1. created node is added to the cluster and connected
2. kcs link https://access.redhat.com/solutions/6471021
3. machine is set to deleting. it must be removed and allowed to come back to the cluster
Expected results:
machine is connected and bmh resources are created
Additional Info:
apiVersion: metal3.io/v1alpha1
kind: BareMetalHost
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"metal3.io/v1alpha1","kind":"BareMetalHost","metadata":{"annotations":{},"name":"eng-gpu-005.acacia.local","namespace":"openshift-machine-api"},"spec":{"bootMACAddress":"90:5a:08:25:b2:fe","bootMode":"UEFI","customDeploy":
,"externallyProvisioned":true,"online":true,"userData":
{"name":"worker-user-data-managed"}}}
creationTimestamp: "2025-08-20T22:41:52Z"
finalizers:
- baremetalhost.metal3.io
generation: 2
name: eng-gpu-005.acacia.local
namespace: openshift-machine-api
resourceVersion: "239938565"
uid: d3c21ffe-2dfb-40af-863a-b3e815d20cd6
spec:
automatedCleaningMode: metadata
bmc:
address: ""
credentialsName: ""
bootMACAddress: 90:5a:08:25:b2:fe
bootMode: UEFI
customDeploy:
method: install_coreos
externallyProvisioned: true
online: true
userData:
name: worker-user-data-managed
status:
errorCount: 0
errorMessage: ""
goodCredentials: {}
lastUpdated: "2025-08-20T22:41:52Z"
operationHistory:
deprovision:
end: null
start: null
inspect:
end: null
start: null
provision:
end: null
start: null
register:
end: null
start: null
operationalStatus: discovered
poweredOn: false
provisioning:
ID: ""
image:
url: ""
state: unmanaged
triedCredentials: {}