grafana_rule_group "Provider produced inconsistent result after apply - Root object was present, but now absent" #2276
Description
Terraform Version
Terraform v1.10.4
Terraform Grafana Provider Version
version = "3.25.2" also tried with version = "3.25.9"
Grafana Version
11.6.0
Affected Resource(s)
No response
Terraform Configuration Files
# providers.tf (root)
terraform {
required_version = ">= 1.10.4"
required_providers {
grafana = {
source = "grafana/grafana"
version = "3.25.9"
}
aws = {
source = "hashicorp/aws"
version = "6.0.0"
}
}
backend "s3" {}
}
# Configure Grafana provider
provider "grafana" {
url = var.grafana_url
auth = local.grafana_api_key
}
Expected Behavior
Terraform should successfully create or update the grafana_rule_group resources without reporting an inconsistent state. The rule groups should remain present in Grafana after a successful terraform apply.
Yesterday, this was working fine without any changes.
Actual Behavior
During terraform apply, I receive warnings indicating that rule groups exist in Terraform state but are missing from Grafana, leading to recreation attempts. Following these warnings, multiple "Error: Provider produced inconsistent result after apply" errors occur for these same grafana_rule_group resources. The provider claims the "Root object was present, but now absent."
Warning: rule group with ID "1::" is in Terraform state, but no longer exists in Grafana │ │ with module.rds_alerts[0].grafana_rule_group.rds_cpu_alerts["qa"], │ on modules/rds/alerts.tf line 5, in resource "grafana_rule_group" "rds_cpu_alerts": │ 5: resource "grafana_rule_group" "rds_cpu_alerts" { │ │ "1::" will be recreated when you apply ╵ ╷ │ Error: Provider produced inconsistent result after apply │ │ When applying changes to │ module.rds_alerts[0].grafana_rule_group.rds_cpu_alerts["qa"], provider │ "provider[\"registry.terraform.io/grafana/grafana\"]" produced an │ unexpected new value: Root object was present, but now absent. │ │ This is a bug in the provider, which should be reported in the provider's │ own issue tracker.
Steps to Reproduce
No response
Important Factoids
No response
References
No response