With the separation of terraform stages, the IAM instance profile for the bootstrap instance may not be ready when the instance is created. The AWS terraform provider should be retrying for 2 minutes in this case. However, there are frequent occurrences of the terraform provider sending a few requests and then not recognizing that it received a response for the last request. In such cases, the terraform provider waits for the remainder of the 2 minutes, but does not attempt any more requests. ~~~~~ time="2021-06-23T14:34:51Z" level=error msg="Error: Error launching source instance: InvalidParameterValue: Value (ci-op-s7yl8r13-76b4f-ktgsq-bootstrap-profile) for parameter iamInstanceProfile.name is invalid. Invalid IAM Instance Profile name" time="2021-06-23T14:34:51Z" level=error msg="\tstatus code: 400, request id: cac73bc7-598c-486a-8263-94629722e775" time="2021-06-23T14:34:51Z" level=error time="2021-06-23T14:34:51Z" level=error msg=" on ../tmp/openshift-install-bootstrap-147975145/main.tf line 136, in resource \"aws_instance\" \"bootstrap\":" time="2021-06-23T14:34:51Z" level=error msg=" 136: resource \"aws_instance\" \"bootstrap\" {" time="2021-06-23T14:34:51Z" level=error time="2021-06-23T14:34:51Z" level=error time="2021-06-23T14:34:51Z" 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"
Thanks Russell. Per comment 2 and comment 4, setting to VERIFIED.
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.9.0 bug fix and 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-2021:3759