When scaling out a baremetal IPI cluster, we create the BMH and bmc secret from yaml. The bmh object skips Ready state and goes straight into provisioning --> provisioned (as if its already associated with a machine).

OCP 4.7.55

In cu environment, repeatable/reproducible every time we reprovision this bmh

1. Delete the bmh / verify deletion of machine/node
2. Recreate bmh/bmc secret
3. Node skips Ready and goes straight to provisioning/provisioned and node tries to register with cluster

1. Create bmh
2. bmh object has no machine defined / no machines reference bmh
3. bmh object skips Ready state (as mentioned in docs) and jumps to provisioning/provisioned
4. kubelet on node tries to register as a node

1. create bmh
2. bmh object goes to Ready
3. Scale out machineset
4. Machine object created and ties to available bmh
5. bmh object goes to Provisioning-->Provisioned
5. Node object gets created and goes ready

must-gather, sosreport and more data can be found in linked support case 03574472.