-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Error: Resource node has no configuration attached #21757
Comments
I came across a similar issue and it was due to an input variable having a wrong type set. It was:
changed it to:
without the quotes. Not sure if that's the same issue but I had the exact same symptoms. I'd review your input types first as per: https://www.terraform.io/docs/configuration/variables.html |
I can reproduce this reliably by specifying invalid type in 0.12.3:
plan works, apply with plan file fails:
Apply without a plan file seems to work. This should error during plan and display a sensible message. |
I don't know what exactly the steps that I did but I got the same errors and the same workaround worked for me. |
We've had the same issue here after upgrading to 0.12 - and the problem was that we defined the same attribute twice on the same ressource :
We removed the extra "target_type" and it works again |
I've produced it in 0.12 with a duplicate |
@sarneaud nice clue. Just to clarify, did you write your |
No, I have multiple It looks like a lot of mistakes like this are showing up as "no configuration attached" errors during |
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. |
Terraform Version
Terraform v0.12.2
Debug Output
I have the trace output but would prefer not to post it here - even encrypted. It contains a lot of sensitive information. Is there an email address @hashicorp I can send it to instead?
Expected Behavior
Successful plan should have applied
Actual Behavior
Received error message for seemingly every resource in every module:
Error: Resource node has no configuration attached
The graph node for
module.aas_resources.module.aas_vm_avzone_creation.azurerm_virtual_machine_extension.oms_extension[0]
has no configuration attached to it. This suggests a bug in Terraform's apply
graph builder; please report it!
Error: Resource node has no configuration attached
The graph node for
module.hana_resources.module.hana_vm_avzone_creation.azurerm_virtual_machine_data_disk_attachment.disk_attachments[7]
has no configuration attached to it. This suggests a bug in Terraform's apply
graph builder; please report it!
Error: Resource node has no configuration attached
The graph node for
module.ci_resources.module.ci_vm_avzone_creation.azurerm_network_interface.nic[0]
has no configuration attached to it. This suggests a bug in Terraform's apply
graph builder; please report it!
Error: Resource node has no configuration attached
The graph node for
module.ci_resources.module.ci_vm_avzone_creation.azurerm_virtual_machine_data_disk_attachment.disk_attachments[3]
has no configuration attached to it. This suggests a bug in Terraform's apply
graph builder; please report it!
Steps to Reproduce
terraform init
terraform plan
terraform apply
Additional Context
We have around 4 layers of modules so it's hard to post a code snippet to describe the problem. The plan comes back green and it looks like everything it wants to create is what it should be creating. Everything worked as it should under TF 0.11.14, we are working through 0.12 changes so we can utilize the new version.
Workaround
I was able to workaround the issue by not using an output file from
terraform plan
and just doing an apply. Unfortunately that is not going to work for us because our pipeline automation doesn't work that way.The text was updated successfully, but these errors were encountered: