hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.75k stars 9.11k forks source link

Increase time to deploy aws_ec2_transit_gateway_connect_peer #23689

Closed mtarnoci closed 5 months ago

mtarnoci commented 2 years ago

Community Note

Terraform v1.1.6

on linux_amd64

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp

Debug Output

Panic Output

Expected Behavior

AWS Provider should wait longer time while waiting for state to become 'available' for aws_ec2_transit_gateway_connect_peer

After 10 minutes, when connect peeri is not "available" yet, terraform fails with error:

Error: error waiting for EC2 Transit Gateway Connect Peer (tgw-connect-peer-0f161e72b4b6df78a) create: timeout while waiting for state to become 'available' (last state: 'pending', timeout: 10m0s) β”‚ β”‚ with aws_ec2_transit_gateway_connect_peer.gre-01-cedge-black["cpe01_vpn2"], β”‚ on 01_ngena-transit-gateway.tf line 270, in resource "aws_ec2_transit_gateway_connect_peer" "gre-01-cedge-black": β”‚ 270: resource "aws_ec2_transit_gateway_connect_peer" "gre-01-cedge-black" After five more minutes is connect peer availble (via console)

Steps to Reproduce

  1. terraform apply

Important Factoids

References

ewbankkit commented 2 years ago

@mtarnoci Thanks for raising the issue πŸ‘. The creation timeout can be increased via a resource-level timeouts block:

resource "aws_ec2_transit_gateway_connect_peer" "example" {
  ...

  timeouts {
    create = "60m"
  }
}
github-actions[bot] commented 6 months ago

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

github-actions[bot] commented 4 months ago

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.