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

**Terraform issues on the .12.12 version: need multiple plan/apply to create the eks infra on aws** #10664

Open
ghost opened this issue Oct 29, 2019 · 2 comments
Labels
waiting-response Maintainers are waiting on response from community or contributor.

Comments

@ghost
Copy link

ghost commented Oct 29, 2019

This issue was originally opened by @vrathore18 as hashicorp/terraform#23221. It was migrated here as a result of the provider split. The original body of the issue is below.


Please do not close this request until we have a fix solution to this

I am using the latest version of Terraform version (0.12.12) but still getting the same issue which is mentioned here: #hashicorp/terraform#4149
But there was not solution provided.

recently upgraded my terraform script for eks. now I am started getting the tiller error and had to plan/apply again and again to make this working.

what could be the possible fix for this issue? Also there was 2 more issue

  1. When I try to destroy the terraform I sometime gets this error:
    Error: Error deleting subnet: timeout while waiting for state to become 'destroyed' (last state: 'pending', timeout: 20m0s)

  2. When I apply the terraform script ACM Certificate Never Validated. It seems to get stuck on the certificate validation. I see messages like this:
    module.dns.aws_acm_certificate_validation.main: Still creating... [38m21s elapsed]

I need to do a manual copy-paste in route53 to make it working.

Could you please looking into the issue.

@vrathore18
Copy link

Folks, any updates on this??

@justinretzolk
Copy link
Member

Hey @vrathore18 👋 Thank you for taking the time to file this issue! Given that there's been a number of AWS provider releases since you initially filed it, can you confirm whether you're still experiencing this behavior?

@justinretzolk justinretzolk added waiting-response Maintainers are waiting on response from community or contributor. and removed needs-triage Waiting for first response or review from a maintainer. labels Dec 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting-response Maintainers are waiting on response from community or contributor.
Projects
None yet
Development

No branches or pull requests

2 participants