us-east-1-iah-2a is a new Local Zone released on Feb. 2024. [1]

EC2 machine was created successfully and running well in us-east-1-iah-2a, but it stuck in Provisioned status:

openshift-machine-api   yunjiang-lz1iah2-f9txv-edge-us-east-1-iah-2a-z6lfg   Provisioned   m6i.xlarge   us-east-1   us-east-1-iah-2a   176m

Checking machine services, kubelet-dependencies.target service not started:

○ kubelet-dependencies.target - Dependencies necessary to run kubelet
 	Loaded: loaded (/etc/systemd/system/kubelet-dependencies.target; static)
 	Active: inactive (dead)
   	Docs: https://github.com/openshift/machine-config-operator/

[1] https://aws.amazon.com/about-aws/whats-new/2024/02/aws-local-zone-houston/

 

4.16.0-0.nightly-2024-06-13-084629
 

Always
 

1. Create cluster with the following config:

 compute:
 - architecture: amd64
   hyperthreading: Enabled
   name: worker
   platform: {}
   replicas: 3
 - architecture: amd64
   hyperthreading: Enabled
   name: edge
   platform:
 	aws:
   	zones:
   	- us-east-1-iah-2a
   replicas: 1
 metadata:
   name: yunjiang-lz1iah2
 platform:
   aws:
 	region: us-east-1

The machine created in us-east-1-iah-2a stuck in Provisioned status.
 

No issues while deploying node in us-east-1-iah-2a
 

No issues in 4.15 TF install