Description of problem:

Using ManagedClusterAddon feature in RHACM 2.14.2 on OCP 4.20 on AWS, submariner fails to come up. According to status, the machine exists and is running, but never reaches "provisioned as node" status.

This behavior is 100% reproducible with community subctl v0.21.0 on a freshly installed OCP 4.20 cluster on AWS

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

Upstream subctl v0.21.0

OCP 4.20/RHACM 2.14.2

How reproducible: 100%

Steps to Reproduce:

1. Install OCP 4.20 cluster on AWS (I have seen it with 4.20.6 and 4.20.14)
2. Run `subctl cloud prepare aws --ocp-metadata ~/gitwork/clusters/r420/metadata.json` (with different metadata)
3. Observe machine "provisioned" but not "node"
4. ...

Actual results: Machine is created but never completes provisioning 

Expected results: Node is provisioned and submariner installation and configuration proceeds and completes

Additional info: