"The graph node for ... has no configuration attached to it" while destroying #31850
Comments
|
Hi @marcincuber, Thanks for filing the issue. We have seen this once before a very long time ago, so I don't know if it's specifically v1.3 related, but it would be great to finally solve how this happened! I'm not sure how you arrived here, but the fact that you saw an error from the resource is a good clue. Is this reproducible, and is it possible to share the complete trace log output? Thanks! |
jbardin
added
waiting-response
|
Hi @jbardin. I managed to reproduce the error on ubuntu. Please see the trace below, it is actually stating that IAM Role is missing required permission. However, Terraform should definitely handle such issue better. |
|
Note that fixing IAM permission issue also allowed terraform to apply successfully. |
|
Hi @marcincuber! Thanks for the additional context. The apply-time error you shared here does seem to be a provider error, because Terraform Core itself doesn't know anything about AWS IAM. The destroy-time error is curious, though. As the error message mentions, this is not something we expect should happen so it seems like you bumped into a Terraform Core bug there which may or may not be related to the provider error you saw first. Do you also have a trace log for that destroy error? It would be helpful to see what exactly Terraform Core was doing when it encountered that error. |
|
Hi @apparentlymart |
|
Further issues for: he graph node has no configuration attached I had further issues with this today: **m│ On Fri, Sep 30, 2022 at 5:34 PM Peter Charleston @.***> |
apparentlymart
changed the title
|
We were able to repro this issue with the following manifest and steps: terraform {
required_providers {
aws = {
source = "hashicorp/aws"
}
}
}
resource "aws_sqs_queue" "test" {
name = "test-queue"
}
The result of this is exit code equal to 1 (which seriously impacts any script that relies on this to succeed) and the following error message: See tf.log for TRACE logs. The error is slightly different if the same scenario is run with custom providers published to a private registry. terraform {
required_providers {
myprovider = {
source = "myregistry.com/mygroup/myprovider"
}
}
}the TRACE is as follows (note that for some reason it's looking for |
jbardin
removed
waiting-response
|
Thanks @weeniearms, that gives us all the info we need! |
This was referenced Oct 19, 2022
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Terraform Configuration Files
Debug Output
Later when I remove the resource I get:
Expected Behavior
It should create the resource
Actual Behavior
failing to apply
Steps to Reproduce
terraform init
terraform apply
Additional Context
In case you think this is aws provider issue, please let me know.
References
No response
The text was updated successfully, but these errors were encountered: