Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws_efs_mount_target takes longer than 10 minutes to deploy #15278

Closed
jrobison-sb opened this issue Sep 22, 2020 · 3 comments · Fixed by #15293
Closed

aws_efs_mount_target takes longer than 10 minutes to deploy #15278

jrobison-sb opened this issue Sep 22, 2020 · 3 comments · Fixed by #15293
Labels
bug Addresses a defect in current functionality. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/efs Issues and PRs that pertain to the efs service.
Milestone

Comments

@jrobison-sb
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

$ terraform version
Terraform v0.12.28
+ provider.aws v3.3.0

Affected Resource(s)

  • aws_efs_mount_target

Terraform Configuration Files

resource "aws_efs_mount_target" "alpha" {
  file_system_id = aws_efs_file_system.foo.id
  subnet_id      = aws_subnet.alpha.id
}

Expected Behavior

The mount target is created without any error in the apply.

Actual Behavior

Sometimes, but not always, a mount target will take longer than 10 minutes to reach the available state. When that happens, the resource creation will timeout and the apply will fail.

Steps to Reproduce

It's sporadic so it can't be reproduced on-demand, but when it happens the only step is just terraform apply while creating an aws_efs_mount_target.

@ghost ghost added the service/efs Issues and PRs that pertain to the efs service. label Sep 22, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Sep 22, 2020
@gdavison gdavison added bug Addresses a defect in current functionality. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. and removed needs-triage Waiting for first response or review from a maintainer. labels Sep 22, 2020
@anGie44 anGie44 added this to the v3.8.0 milestone Sep 24, 2020
@anGie44
Copy link
Contributor

anGie44 commented Sep 24, 2020

A fix to increase the create timeout has been merged and will release with v3.8.0 of the Terraform AWS Provider, likely out later today.

@ghost
Copy link

ghost commented Sep 24, 2020

This has been released in version 3.8.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks!

@ghost
Copy link

ghost commented Oct 25, 2020

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Oct 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. good first issue Call to action for new contributors looking for a place to start. Smaller or straightforward issues. service/efs Issues and PRs that pertain to the efs service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants