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

Post terraform destroy errors #3377

Closed
jasonkuhrt opened this issue Oct 1, 2015 · 11 comments
Closed

Post terraform destroy errors #3377

jasonkuhrt opened this issue Oct 1, 2015 · 11 comments
Labels
bug core waiting-response An issue/pull request is waiting for a response from the community

Comments

@jasonkuhrt
Copy link

I'm using Atlas to manage state. After running terraform destroy locally I finish with the error pasted below. The actual destruction appears to complete so I'm not sure what this error is all about. What's going on? Seems like a bug to me.

Error applying plan:

8 error(s) occurred:

* Resource 'aws_elb.service' does not have attribute 'id' for variable 'aws_elb.service.id'
* Resource 'aws_elb.service' does not have attribute 'dns_name' for variable 'aws_elb.service.dns_name'
* Resource 'aws_elb.service' does not have attribute 'id' for variable 'aws_elb.service.id'
* Resource 'aws_elb.service' does not have attribute 'dns_name' for variable 'aws_elb.service.dns_name'
* Resource 'aws_elb.service' does not have attribute 'dns_name' for variable 'aws_elb.service.dns_name'
* Resource 'aws_elb.service' does not have attribute 'id' for variable 'aws_elb.service.id'
* Resource 'template_file.cloud_config' does not have attribute 'rendered' for variable 'template_file.cloud_config.rendered'
* Resource 'template_file.cloud_config' does not have attribute 'rendered' for variable 'template_file.cloud_config.rendered'

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.
@radeksimko
Copy link
Member

Can you provide a config used (minus any secrets), so we can reproduce it?

I think it may be related to #2892

@jasonkuhrt
Copy link
Author

@radeksimko The config is very large and spans many files. Would be difficult to dump as text here and I do not think I can give you access to our private repo. Is there a subset of the configuration that would be useful?

@radeksimko
Copy link
Member

@jasonkuhrt I just merged #3393 , would you mind pulling down the latest version, building from source and confirming that it has fixed the issue?

@radeksimko radeksimko added the waiting-response An issue/pull request is waiting for a response from the community label Oct 3, 2015
@jasonkuhrt
Copy link
Author

I will try this Monday.

@jasonkuhrt
Copy link
Author

@radeksimko To avoid fumbling around can you explain or link me to instructions for building from source.

@radeksimko
Copy link
Member

@jasonkuhrt Try following this part of the readme: https://github.com/hashicorp/terraform#developing-terraform

@josephholsten
Copy link
Contributor

I'd like to mention I've been having this Resource 'foo' does not have attribute 'id' for variable 'foo.id' issue quite a bit recently. It's being a complete pain trying to create a minimal reproduction case. At this point, I can only reliably reproduce it with a module which passes a computed variable into a sub-module, and with a tfstate which is inaccurate (by destroying resources or creating conflicting resources). I'm getting closer, but it's going to take a bit.

@josephholsten
Copy link
Contributor

oh, I should mention that it not only locks up this way with terraform destroy but also with terraform plan and terraform refresh.

@jasonkuhrt
Copy link
Author

@radeksimko HEAD seems to have fixed this:

❯ ~/go/src/github.com/hashicorp/terraform/bin/terraform destroy

Do you really want to destroy?
  Terraform will delete all your managed infrastructure.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes

<<REDACTED>>

Apply complete! Resources: 0 added, 0 changed, 15 destroyed.

@radeksimko
Copy link
Member

@jasonkuhrt Thanks for testing it! I will close this one then.

@josephholsten Can you please create a new issue and attach a reproduction case?

@ghost
Copy link

ghost commented Apr 30, 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 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.

@ghost ghost locked and limited conversation to collaborators Apr 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug core waiting-response An issue/pull request is waiting for a response from the community
Projects
None yet
Development

No branches or pull requests

3 participants