The Installer is checking the wrong quota when the user selected G or VT instance types. The installer only knows about "Standard (A, C, D, H, I, M, R, T, Z) instances" and assumes that everything else falls under "X instances". The installer should instead be checking the quotas for "G and VT instances". This is a deficiency in the validation around available quota in the user's account. There is a current workaround for the customer to either (1) have the user increase their quota for X instances or (2) have the user use an IAM user that does not have permission to check quota.
verified. PASS. aws service-quotas list-service-quotas --service-code=ec2 --query 'Quotas[?QuotaCode==`L-DB2E81BA`]' | jq .[].Value 920 aws ec2 describe-instance-types --instance-types g3.16xlarge | jq '.InstanceTypes[].VCpuInfo.DefaultVCpus' 64 install-config.yaml: compute: - architecture: amd64 hyperthreading: Enabled name: worker platform: aws: type: g3.16xlarge replicas: 12 controlPlane: architecture: amd64 hyperthreading: Enabled name: master platform: aws: type: g3.16xlarge replicas: 3 error message: FATAL failed to fetch Cluster: failed to fetch dependency of "Cluster": failed to generate asset "Platform Quota Check": error(MissingQuota): ec2/L-DB2E81BA is not available in us-east-2 because the required number of resources (960) is more than the limit of 920
OCP version: 4.10.0-0.nightly-2022-01-24-070025
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056