Feature: AWS "not specifying an Availability Zone in request"

It would be great for CI purposes to not fail on a specified available zone not available.

For my team's testing purposes it generally does not matter what zone a node is in as long as we get a cluster that is healthy and running.

Will resolve CI installer issues related to available instance capacity in a zone.

level=error
level=error msg=Error: Error launching source instance: InsufficientInstanceCapacity: We currently do not have sufficient m6a.xlarge capacity in the Availability Zone you requested (us-east-1d). Our system will be working on provisioning additional capacity. You can currently get m6a.xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1a, us-east-1b, us-east-1c, us-east-1f.
level=error msg=	status code: 500, request id: 9bb90ecd-8fd4-46d4-add4-99df87f249a6
level=error
level=error msg=  on ../tmp/openshift-install-138240719/master/main.tf line 129, in resource "aws_instance" "master":
level=error msg= 129: resource "aws_instance" "master" {
level=error
level=error
push_pin
level=fatal msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: failed to complete the change
Installer exit with code 1

Start by tracing the installer path that generates the Terraform aws_instance resource shown at main.tf line 129, then inspect how the Availability Zone is selected or passed to AWS. Reproduce the insufficient-capacity failure in CI or an equivalent test environment and define completion as a healthy cluster being created without requiring an unavailable zone.