[Bug]: Duplicate Entry for protocol_access_rules.client_ip

[brent-at-aam]

Terraform Core Version

1.9.6

ONTAP Provider Version

1.1.4

Affected Resource(s)

netapp-ontap_protocols_nfs_service_resource

Expected Behavior

Should be able to create the resource.

Actual Behavior

Resource creation fails with an error message that there is a duplicate entry for protocol_access_rules.client_ip. This is not a field we have access to set.

Relevant Error/Panic Output Snippet

╷
│ Error: error creating NFS services
│ 
│   with netapp-ontap_protocols_nfs_service_resource.foo,
│   on main.tf line 47, in resource "netapp-ontap_protocols_nfs_service_resource" "foo":
│   47: resource "netapp-ontap_protocols_nfs_service_resource" "foo" {
│ 
│ error on POST protocols/nfs/services: REST reported error
│ restclient.RestError{Code:"1", Message:"duplicate entry",
│ Target:"protocol_access_rules.client_ip"}, statusCode: 409, statusCode 409
╵

Terraform Configuration Files

provider "netapp-ontap" {
  connection_profiles = [
    {
      name           = "OUR_NAME"
      hostname       = "OUR_HOSTNAME"
      username       = "OUR_USERNAME"
      password       = "OUR_PASSWORD"
      validate_certs = false
    }
  ]
}

resource "netapp-ontap_protocols_nfs_service_resource" "foo" {
  cx_profile_name = var.filesystem
  svm_name        = var.svm_name
  enabled         = true
  protocol = {
    v3_enabled  = true
    v40_enabled = true
    v40_features = {
      acl_enabled = true
    }
    v41_enabled = true
    v41_features = {
      acl_enabled = true
    }
    v4_id_domain = var.domain
  }
}

Steps to Reproduce

Run terraform plan/apply

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

No

[chuyich]

@brent-at-aam Would you please provide the log by running:
TF_LOG="DEBUG" terraform apply
So we will have clear picture to see what happened. Thanks.

[carchi8py]

@brent-at-aam can you send that log to me at carchi@netapp.com or @chuyich at chuyi.ching@netapp.com

[csahu9]

@brent-at-aam The mentioned issue couldn't be reproduced in house. Creating NFS configuration using resource netapp-ontap_nfs_service worked as expected.

REST error duplicate entry is usually thrown when we try to create an entity that already exists.
Could you refer to the resource documentation and try importing existing NFS config and run terraform apply to see if idempotency is observed?