provider/aws: Increase route_table timeouts

[carlossg]

It may take more than 1 minute

21:01:58 [vpc] aws_route_table.public: Refreshing state... (ID: rtb-d202deb4)
21:01:58 [vpc] aws_route_table_association.jce-public: Refreshing state... (ID: rtbassoc-248f4a5d)
21:02:00 [vpc] aws_route_table_association.jce-public: Destroying...
21:02:00 [vpc] aws_route_table_association.jce-public: Destruction complete
21:02:00 [vpc] aws_route_table.public: Destroying...
21:02:12 [vpc] aws_route_table.public: Still destroying... (10s elapsed)
21:02:22 [vpc] aws_route_table.public: Still destroying... (20s elapsed)
21:02:32 [vpc] aws_route_table.public: Still destroying... (30s elapsed)
21:02:40 [vpc] aws_route_table.public: Still destroying... (40s elapsed)
21:02:50 [vpc] aws_route_table.public: Still destroying... (50s elapsed)
21:03:00 [vpc] aws_route_table.public: Still destroying... (1m0s elapsed)
21:03:01 [vpc] Error applying plan:
21:03:01 [vpc] 
21:03:01 [vpc] 1 error(s) occurred:
21:03:01 [vpc] 
21:03:01 [vpc] * aws_route_table.public: Error waiting for route table (rtb-d202deb4) to become destroyed: timeout while waiting for state to become ''. last error: %!s(<nil>)

[radeksimko]

Hi @carlossg
thanks for the PR. I can see the error message here could also be a bit more useful than it is, which is why I opened a separate PR to fix that. #8510

[carlossg]

Thanks @radeksimko !

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.