I'd check Route 53 first. Then I'd make sure your AWX credentials have the proper access.
For OpenShift IPI on AWS, the **base domain must already exist as a valid Route 53 hosted zone**, and the installer will create the cluster subdomain records under:
cluster-name.base-domain
Example: maximodemo.dummydomain.com
So that part is expected. IBM's AWS install docs note that MAS/OpenShift uses a public hosted zone for cluster access/DNS routing.
I'd suggest checking:
aws route53 list-hosted-zones | grep dummydomain.com
Then confirm the zone is in the same AWS account being used by mas provision-aws.
The multiple VPCs are likely from repeated installer retries/failures where cleanup did not complete. I'd clean up any failed cluster resources before re-running, or use a fresh unique cluster name.
I would also verify that dummydomain.com is not just used by other resources, but is actually delegated correctly in Route 53 and can support a new child cluster domain.
Most likely issue:
DNS/base domain hosted zone mismatch
stale failed install resources, or
the AWS credentials don't have full permissions to manage DNS resources.
------------------------------
Shauna Gilbert
Naviam
------------------------------