Closed pulumi-bot closed 7 months ago
The error in all cases above was:
aws-native:ec2:SubnetRouteTableAssociation (VPCPublicSubnet1RouteTableAssociation0B0896DC):
error: reading resource state: reading resource state: operation error CloudControl: GetResource, https response error StatusCode: 400, RequestID: fca75fd6-63d7-4569-8853-49f8558a8242, ResourceNotFoundException: AWS::EC2::SubnetRouteTableAssociation Handler returned status FAILED: No route tables Found with association rtbassoc-03189a84b8caa818f (HandlerErrorCode: NotFound, RequestToken: 81dddeca-f9da-44a5-9b93-9ff127dfb1c4)
This mostly happened in the ALB test, but also once in the Fargate test.
AFAICT, this is an intermittent bug with the CC API where an AWS::EC2::SubnetRouteTableAssociation
isn't always found immediately after it's created.
I don't think "Not Found" errors are retried by default in the cloud control client used by aws-native (and doing so would create artificial slowdowns when there are legit not founds).
We can file a bug against Cloud Control, but in the meantime, we will need to either disable these tests or retry them to avoid the flaky results
Workflow Failure
main has failed. See the list of failures below:
2023-11-15T07:29:00.000Z
2023-11-15T16:54:11.000Z
2023-11-16T07:27:27.000Z
2023-11-18T07:45:55.000Z
2023-11-21T07:36:10.000Z
2023-11-22T07:34:01.000Z