terraform-provider-newrelic: Error: expected entity tag team to have been updated but was not found
Please include the following with your bug report
⚠️ Important: Failure to include the following, such as omitting the Terraform configuration in question, may delay resolving the issue.
- [x ] Your New Relic
providerconfiguration (sensitive details redacted) - [ x] A list of affected resources and/or data sources
- [x ] The configuration of the resources and/or data sources related to the bug report (i.e. from the list mentioned above)
- [x ] Description of the current behavior (the bug)
- [ x] Description of the expected behavior
- [ x] Any related log output
Terraform Version
Terraform v1.0.11
on linux_amd64
+ provider registry.terraform.io/newrelic/newrelic v2.34.0
Affected Resource(s)
newrelic_entity_tags.nr_dashboard_tags
issue seen v2.30.0, v2.30.2 and v2.34.0
Terraform Configuration
https://gist.github.com/thedebugger/2e26fbb8ca484d464a0701f98f8a0d27
Actual Behavior
terraform errored with " expected entity tag team to have been updated but was not found"
Expected Behavior
terraform should update the nr_dashboard_tags accordingly
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
- Create nr_one_dashboard and nr_dashboard_tags
- Delete the dashboard resource manually from state file and from NR (or manually change the nr_dashboard_tags to something non-existent)
- run terraform apply
Debug Output
Can provide debug output if required since we have hundred of resources. But here are the info logs https://gist.github.com/thedebugger/2e26fbb8ca484d464a0701f98f8a0d27
Important Factoids
no
References
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 27 (12 by maintainers)
This was raised with the alerting team internally as there is nothing we can do on the Terraform side to fix this issue. As mentioned retry mechanism timeout has been raised to 60 seconds which will hopefully avoid the error we’ve been seeing.
As there is no action we can take on the Terraform side we will close the ticket. Feel free to continue the discussion if needed.
I had tried it with
parallelism=2back when I encountered this issue early last month, and doing that did not remove the error (i.e. yes, I still saw the issue then). I haven’t come back to it since. We did work around it by using python to generate a terraform file with no looping, just a separate structure for each item.Just an update on this. This happens only when you use
countorfor_eachon the resource (creating multiplenewrelic_entity_tags resources). Apparently, creating multiple tags using a singlenewrelic_entity_tagsresource would not produce described behavior. One way to circumvent this is to create separatenewrelic_entity_tagsresource for each entity and to use Terraformdynamickeyword on thetagblock. EXAMPLE:Yes, this was on the latest version. I setup autopatching for a reason.
I’m quitting this job Friday, so how would I generate a debug log?
I will confirm that we are still seeing this issue in Terraform provider version 3.0.2
s: Still creating… [20s elapsed] ╷ │ Error: expected entity tag type to have been updated but was not found │ │ with module.cluster_alerts.module.synthetic_slash_alert.newrelic_entity_tags.this_tags, │ on …/modules/newrelic_alert/main.tf line 51, in resource “newrelic_entity_tags” “this_tags”: │ 51: resource “newrelic_entity_tags” “this_tags” {