Fail to create BMCEventSubscription in multicluster with error "Node xxx could not be found"

[Description of problem:
In a typical multi-cluster ACM deployment, when create a BMCEventSubscription CR against a spoke cluster, the CR has to be created in the hub cluster since BMHs for spoke clusters are managed in the hub cluster.

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

How reproducible:
Always.

Steps to Reproduce:
===================
$ oc apply -f BMCEventSubscription.yaml

The subscription yaml used:
$ cat BMCEventSubscription.yaml
apiVersion: metal3.io/v1alpha1
kind: BMCEventSubscription
metadata:
name: sub-02
namespace: worker-2
spec:
hostName: worker-2.cluster1.savanna.lab.eng.rdu2.redhat.com
destination: https://hw-event-proxy-openshift-bare-metal-events.worker-2.cluster1.savanna.lab.eng.rdu2.redhat.com/webhook
context: ''

Actual results:
===============
$ oc -n worker-2 get BMCEventSubscription
NAME ERROR AGE
sub-02 failed to create a subscription 8m31s

$ oc -n openshift-machine-api logs -f metal3-758cd646f8-vspk9 metal3-ironic-api
....
2022-07-05 21:45:25.893 46 DEBUG ironic.api.method [req-fa842d3e-78a8-4ea3-9c34-2c568d9b8aef ironic-user - - - -] Client-side error: Node 2519fcee-5ea7-4418-856f-1f8c207221eb could not be found. format_exception /usr/lib/python3.6/site-packages/ironic/api/method.py:124
2022-07-05 21:45:25.894 46 INFO eventlet.wsgi.server [req-fa842d3e-78a8-4ea3-9c34-2c568d9b8aef ironic-user - - - -] ::1 "POST /v1/nodes/2519fcee-5ea7-4418-856f-1f8c207221eb/vendor_passthru?method=create_subscription HTTP/1.1" status: 404 len: 462 time: 0.0215096

Expected results:
=================
BMCEventSubscription created successfully.

Additional info:
================
Here is the information on spoke cluster worker-2 which this subscription targets to:
$ oc -n worker-2 get bmh worker-2.cluster1.savanna.lab.eng.rdu2.redhat.com -o json | jq .spec.bmc
{
"address": "idrac-VirtualMedia://[2620:52:0:1bd:a5bc:709c:1fa1:c4bb]/redfish/v1/Systems/System.Embedded.1",
"credentialsName": "worker-2-bmc-secret",
"disableCertificateVerification": true
}

$ oc -n worker-2 get bmh worker-2.cluster1.savanna.lab.eng.rdu2.redhat.com -o json | jq .status.hardware.hostname
"worker-2.cluster1.savanna.lab.eng.rdu2.redhat.com"

$ oc -n worker-2 get bmh worker-2.cluster1.savanna.lab.eng.rdu2.redhat.com -o json | jq .status.provisioning.ID
"2519fcee-5ea7-4418-856f-1f8c207221eb"