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