Bug 2064969
| Summary: | AWS eventual consistency with route table: empty result when reading | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Matthew Staebler <mstaeble> |
| Component: | Installer | Assignee: | Patrick Dillon <padillon> |
| Installer sub component: | openshift-installer | QA Contact: | Yunfei Jiang <yunjiang> |
| Status: | CLOSED DEFERRED | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | padillon, talessio |
| Version: | 4.11 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.12.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-03-09 01:15:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Per CI logs [1], still saw some `error reading Main Route Table Association` errors [2]. [1] https://search.ci.openshift.org/?search=error+reading+Main+Route+Table+Association&maxAge=168h&context=5&type=build-log&name=.*4%5C.11.*aws.*&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job [2] https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-upgrade/1506420355831435264 We recently hit such issues, including Prow CI [1][2] and manually install. [1]4.12 https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-multiarch-master-nightly-4.12-ocp-e2e-aws-sdn-arm64/1565834051758067712 [2]4.11 https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-fips/1565592292461383680 OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira. https://issues.redhat.com/browse/OCPBUGS-9176 |
level=error level=error msg=Error: error reading Main Route Table Association (rtbassoc-047bc7d14b5e0a695): empty result level=error level=error msg= with module.vpc.aws_main_route_table_association.main_vpc_routes[0], level=error msg= on vpc/vpc-public.tf line 27, in resource "aws_main_route_table_association" "main_vpc_routes": level=error msg= 27: resource "aws_main_route_table_association" "main_vpc_routes" { level=error level=fatal msg=failed to fetch Cluster: failed to generate asset "Cluster": failed to create cluster: failed to apply Terraform: exit status 1 level=fatal level=fatal msg=Error: error reading Main Route Table Association (rtbassoc-047bc7d14b5e0a695): empty result level=fatal level=fatal msg= with module.vpc.aws_main_route_table_association.main_vpc_routes[0], level=fatal msg= on vpc/vpc-public.tf line 27, in resource "aws_main_route_table_association" "main_vpc_routes": level=fatal msg= 27: resource "aws_main_route_table_association" "main_vpc_routes" { level=fatal level=fatal https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_installer/5715/pull-ci-openshift-installer-master-okd-e2e-aws-upgrade/1504180939054387200 This issue was reported against the terraform provider [1]. There was a fix introduced in 4.0.0 of the terraform provider. There are reports of further route table problems in 4.0.0, though. [1] https://github.com/hashicorp/terraform-provider-aws/issues/21629