Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

code: 400, message: Error updating volume - Cannot specify NFSv3 export policy rules for non-NFSv3 volume #92

Open
red73ver opened this issue Mar 19, 2024 · 2 comments

Comments

@red73ver
Copy link

red73ver commented Mar 19, 2024

netapp-gcp provider version = "23.12.0"
terraform version = v1.7.5 ( linux_amd64 )

This particular version of provider (23.12.0) does have a problem to create or update NFSv4 volume:

  name           = "my-cvs-vol-nfs"
  region         = var.region
  protocol_types = ["NFSv4"]
  network        = data.google_compute_network.my_vpc.name
  volume_path    = "my-cvs-vol-nfs"
  size           = 100
  service_level  = "extreme"
  storage_class  = "hardware"

  export_policy {
    rule {
      allowed_clients = "10.0.1.0/24"
      access          = "ReadWrite"
      nfsv3 {
        checked = false
      }
      nfsv4 {
        checked = true
      }
    }
  }
}

It results in error

Error: code: 400, message: Error updating volume - Cannot specify NFSv3 export policy rules for non-NFSv3 volume

Problem also exist when terraform check existing volumes created using previous version of provider, and trying to remove and add exactly the same block of "export_policy" as below.

  - export_policy {
          - rule {
              - access               = "ReadWrite" -> null
              - allowed_clients      = "10.0.1.0/24" -> null
              - has_root_access      = "true" -> null
              - kerberos5_readonly   = false -> null
              - kerberos5_readwrite  = false -> null
              - kerberos5i_readonly  = false -> null
              - kerberos5i_readwrite = false -> null
              - kerberos5p_readonly  = false -> null
              - kerberos5p_readwrite = false -> null

              - nfsv3 {
                  - checked = false -> null
                }

              - nfsv4 {
                  - checked = true -> null
                }
            }
        }
      + export_policy {
          + rule {
              + access               = "ReadWrite"
              + allowed_clients      = "10.0.1.0/24"
              + kerberos5_readonly   = false
              + kerberos5_readwrite  = false
              + kerberos5i_readonly  = false
              + kerberos5i_readwrite = false
              + kerberos5p_readonly  = false
              + kerberos5p_readwrite = false

              + nfsv3 {
                  + checked = false
                }

              + nfsv4 {
                  + checked = true
                }
            }
        }

In this case terraform also fail with the same code as above.

Described problem exist only in 23.12.0 version of this provider. Version 23.4.0 seems to be completely fine.

okrause added a commit to okrause/terraform-provider-netapp-gcp that referenced this issue Mar 19, 2024
- Fix for issue NetApp#90
- Fix for issue NetApp#92
@okrause
Copy link
Contributor

okrause commented Mar 19, 2024

I can confirm the issue. Additionally to the NFSv3/NFSv4 issue, plans are not stable since f3a8f75, which is bad.

@okrause
Copy link
Contributor

okrause commented Apr 4, 2024

@red73ver A new version was released. I is supposed to fix your issues. Please check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants