[BUG] creating AAAA DNS record fails sometimes

[Koe-Greg]

Describe the bug

From time to time, Provider produced inconsistent final plan when creating AAAA DNS record

Terraform Version

Terraform v1.5.7

OVH Terraform Provider Version

ovh/ovh v1.6.0 (signed by a HashiCorp partner, key ID F56D1A6CBDAAADA5)

Affected Resource(s)

resources:

• ovh_domain_zone_record

Terraform Configuration Files

nodes = {
  node1 = {
    name                = "node1"
    server_type         = "cpx31"
  }
}

resource "ovh_domain_zone_record" "server_dns_record_AAAA" {
  for_each = var.nodes

  zone      = "koopilot.tech"
  subdomain = each.value.name
  fieldtype = "AAAA"
  ttl       = 3600
  target    = hcloud_server.cloud_nodes[each.key].ipv6_address
}

Expected Behavior

user@server:~$ terraform apply
[...]
ovh_domain_zone_record.server_dns_record_AAAA["vmphch104"]: Creating...
ovh_domain_zone_record.server_dns_record_AAAA["vmphch104"]: Creation complete after 1s [id=5354269568]

Actual Behavior

user@server:~$ terraform apply
[...]
│
│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for
│ ovh_domain_zone_record.server_dns_record_AAAA["node1"] to include new
│ values learned so far during apply, provider
│ "registry.terraform.io/ovh/ovh" produced an invalid new value for .target:
│ was cty.StringVal(""), but now cty.StringVal("2a01:4f9:c013:87b::1").
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
│

Additional context

This code have been used a 100s of time and failed twice so far with same output.
Running same code a second time makes creation successful.

terraform plan always present the same creation action:

 user@server:~$ terraform apply
[...]
 # ovh_domain_zone_record.server_dns_record_AAAA["node1"] will be created
  + resource "ovh_domain_zone_record" "server_dns_record_AAAA" {
      + fieldtype = "AAAA"
      + id        = (known after apply)
      + subdomain = "node1"
      + ttl       = 3600
      + zone      = "koopilot.tech"
    }

[amstuta]

Hello @Koe-Greg,

Thanks for opening this issue. Unfortunately I'm unable to reproduce this problem, would you be able to retrieve or get new error logs using TF_LOG=debug ?

[Koe-Greg]

Hi Arthur, I will enable it by default and provide you the results when it pops up. Cheers,

…

-- Grégory

On 26 Feb 2025, at 10:44, Arthur Amstutz ***@***.***> wrote: amstuta left a comment (ovh/terraform-provider-ovh#860) Hello @Koe-Greg, Thanks for opening this issue. Unfortunately I'm unable to reproduce this problem, would you be able to retrieve or get new error logs using TF_LOG=debug ? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned. <https://github.com/Koe-Greg> <#860 (comment)> <https://github.com/notifications/unsubscribe-auth/AWIPSJ66GOQEU3MVGQ7MJQL2RWEIHAVCNFSM6AAAAABXUDXPP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBUGQ2DEOBYG4> amstuta left a comment (ovh/terraform-provider-ovh#860) <#860 (comment)> Hello @Koe-Greg <https://github.com/Koe-Greg>, Thanks for opening this issue. Unfortunately I'm unable to reproduce this problem, would you be able to retrieve or get new error logs using TF_LOG=debug ? — Reply to this email directly, view it on GitHub <#860 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWIPSJ66GOQEU3MVGQ7MJQL2RWEIHAVCNFSM6AAAAABXUDXPP6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBUGQ2DEOBYG4>. You are receiving this because you were mentioned.