Bug 1766691 - Timeout for aws_route53_record
Summary: Timeout for aws_route53_record
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Abhinav Dahiya
QA Contact: Johnny Liu
Depends On:
TreeView+ depends on / blocked
Reported: 2019-10-29 16:46 UTC by Oleg Bulatov
Modified: 2020-07-13 17:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Rate limiting from AWS would cause failure to create records for the cluster Consequence: Rate limiting from AWS would cause failure to create records for the cluster Fix: Use exponential back-off to allow for longer wait timeout. Result: Less failures due to Rate limiting
Clone Of:
Last Closed: 2020-07-13 17:12:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Github openshift installer pull 3140 None closed bug 1766691: go.mod: bump terraform-provider-aws to v2.49.0 2020-09-16 02:53:44 UTC
Github terraform-providers terraform-provider-aws pull 11895 None closed aws_route53_record: add create,update,delete timeout options for the resource 2020-09-16 02:53:44 UTC
Red Hat Product Errata RHBA-2020:2409 None None None 2020-07-13 17:12:27 UTC

Description Oleg Bulatov 2019-10-29 16:46:58 UTC


level=error msg="Error: [ERR]: Error building changeset: timeout while waiting for state to become 'accepted' (timeout: 5m0s)"
level=error msg="  on ../tmp/openshift-install-771650541/route53/base.tf line 33, in resource \"aws_route53_record\" \"api_external\":"
level=error msg="  33: resource \"aws_route53_record\" \"api_external\" {"
level=fatal msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to apply using Terraform"

Comment 1 Scott Dodson 2020-01-31 18:43:29 UTC
Proposed to bump the timeout.

Comment 3 Abhinav Dahiya 2020-02-04 23:03:44 UTC
proposed addition of timeout to the resource upstream with the PR https://github.com/terraform-providers/terraform-provider-aws/pull/11895
Only after upsteam accepts the change, we can bump our vendor, and bumping aws provider is blocked on Go modules migration. So in inclined to moving it to 4.5. but let's wait and see.

Comment 8 errata-xmlrpc 2020-07-13 17:12:05 UTC
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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.