With OCP 4.13.0-0.nightly-2023-03-11-033820 hub cluster with advanced-cluster-management.v2.8.0-75 operator installed, we are unable to deploy a spoke SNO cluster due to bmh stuck at provisioning. 


[kni@registry.kni-qe-11 ~]$ oc get bmh -A
NAMESPACE               NAME                                    STATE                    CONSUMER                   ONLINE   ERROR   AGE
kni-qe-25               sno.kni-qe-25.lab.eng.rdu2.redhat.com   provisioning                                        true             28m

Events:
  Type    Reason               Age   From                         Message
  ----    ------               ----  ----                         -------
  Normal  Registered           29m   metal3-baremetal-controller  Registered new host
  Normal  BMCAccessValidated   29m   metal3-baremetal-controller  Verified access to BMC
  Normal  ProfileSet           29m   metal3-baremetal-controller  Hardware profile set: unknown
  Normal  ProvisioningStarted  27m   metal3-baremetal-controller  Image provisioning started for


Saw following error: 

dial tcp 100.24.241.225:443: connect: network is unreachable\n"

This address looks like an EC2 instance
$ host 100.24.241.225
225.241.24.100.in-addr.arpa domain name pointer ec2-100-24-241-225.compute-1.amazonaws.com.

ith OCP 4.13.0-0.nightly-2023-03-11-033820 hub cluster with advanced-cluster-management.v2.8.0-75 operator 

always

1. Deploy hub cluster with above versions
2. Attempt to deploy SNO spoke cluster with 4.13 nightly
3.

Deployment fails. 

Spoke cluster deploys successfully

Workaround so far is to deploy OCP 4.12 with ACM 2.7.2 on hub cluster and deploy spoke with that.

must-gather, rendered CRs and full assisted-service log will be attached