registration error when scale up baremetal server

scale up one baremental worker always show registration error with following information

# oc describe bmh sriov27 -n openshift-machine-api
Name:         sriov27
Namespace:    openshift-machine-api
Labels:       <none>
Annotations:  <none>
API Version:  metal3.io/v1alpha1
Kind:         BareMetalHost
Metadata:
  Creation Timestamp:  2023-05-23T11:19:57Z
  Finalizers:
    baremetalhost.metal3.io
  Generation:  1
  Managed Fields:
    API Version:  metal3.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .:
          v:"baremetalhost.metal3.io":
    Manager:      baremetal-operator
    Operation:    Update
    Time:         2023-05-23T11:19:57Z
    API Version:  metal3.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
      f:spec:
        .:
        f:automatedCleaningMode:
        f:bmc:
          .:
          f:address:
          f:credentialsName:
        f:online:
    Manager:      kubectl-client-side-apply
    Operation:    Update
    Time:         2023-05-23T11:19:57Z
    API Version:  metal3.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:errorCount:
        f:errorMessage:
        f:errorType:
        f:goodCredentials:
        f:hardwareProfile:
        f:lastUpdated:
        f:operationHistory:
          .:
          f:deprovision:
            .:
            f:end:
            f:start:
          f:inspect:
            .:
            f:end:
            f:start:
          f:provision:
            .:
            f:end:
            f:start:
          f:register:
            .:
            f:end:
            f:start:
        f:operationalStatus:
        f:poweredOn:
        f:provisioning:
          .:
          f:ID:
          f:bootMode:
          f:image:
            .:
            f:url:
          f:state:
        f:triedCredentials:
          .:
          f:credentials:
          f:credentialsVersion:
    Manager:         baremetal-operator
    Operation:       Update
    Subresource:     status
    Time:            2023-05-23T11:38:29Z
  Resource Version:  39883
  UID:               447dbc1d-1db7-4937-8fbd-602ec7269d10
Spec:
  Automated Cleaning Mode:  metadata
  Bmc:
    Address:           ipmi://10.9.21.72
    Credentials Name:  openshift-sriov27-bmc-secret
  Online:              true
Status:
  Error Count:    5
  Error Message:  MAC address  conflicts with existing node openshift-machine-api~sriov-worker-1
  Error Type:     registration error
  Good Credentials:
  Hardware Profile:  
  Last Updated:      2023-05-23T11:38:29Z
  Operation History:
    Deprovision:
      End:    <nil>
      Start:  <nil>
    Inspect:
      End:    <nil>
      Start:  <nil>
    Provision:
      End:    <nil>
      Start:  <nil>
    Register:
      End:             <nil>
      Start:           2023-05-23T11:19:57Z
  Operational Status:  error
  Powered On:          false
  Provisioning:
    ID:         
    Boot Mode:  UEFI
    Image:
      URL:  
    State:  registering
  Tried Credentials:
    Credentials:
      Name:               openshift-sriov27-bmc-secret
      Namespace:          openshift-machine-api
    Credentials Version:  32893
Events:
  Type    Reason             Age   From                         Message
  ----    ------             ----  ----                         -------
  Normal  RegistrationError  30m   metal3-baremetal-controller  MAC address  conflicts with existing node openshift-machine-api~sriov-worker-1
  Normal  RegistrationError  30m   metal3-baremetal-controller  MAC address  conflicts with existing node openshift-machine-api~sriov-worker-1
  Normal  RegistrationError  28m   metal3-baremetal-controller  MAC address  conflicts with existing node openshift-machine-api~sriov-worker-1
  Normal  RegistrationError  23m   metal3-baremetal-controller  MAC address  conflicts with existing node openshift-machine-api~sriov-worker-1
  Normal  RegistrationError  11m   metal3-baremetal-controller  MAC address  conflicts with existing node openshift-machine-api~sriov-worker-1

4.12

1. setup cluster with IPI baremetal
2. scale up another baremetal server as worker
3.

# oc get bmh -A
NAMESPACE               NAME             STATE                    CONSUMER                     ONLINE   ERROR                AGE
openshift-machine-api   sriov-master-0   externally provisioned   sriov-b8hcz-master-0         true                          71m
openshift-machine-api   sriov-master-1   externally provisioned   sriov-b8hcz-master-1         true                          71m
openshift-machine-api   sriov-master-2   externally provisioned   sriov-b8hcz-master-2         true                          71m
openshift-machine-api   sriov-worker-0   provisioned              sriov-b8hcz-worker-0-dn87v   true                          71m
openshift-machine-api   sriov-worker-1   provisioned              sriov-b8hcz-worker-0-4xwcm   true                          71m
openshift-machine-api   sriov-worker-2   provisioned              sriov-b8hcz-worker-0-n4hpn   true                          71m
openshift-machine-api   sriov24          provisioned              sriov-b8hcz-worker-0-bn4s9   true                          28m
openshift-machine-api   sriov27          registering                                           true     registration error   28m