proxmox API returned new disk parameter 'wwn' we cannot process`

[KaloyanHr]

Description

I am getting the following error when running terraform plan/apply after the Proxmox CSI Plugin has created disks:
proxmox Provider Error: proxmox API returned new disk parameter 'wwn' we cannot process

I'm using the Telmate/proxmox provider. I have read other issues/discussions related to this such as #363

I had this added in my module before even starting to test the proxmox csi plugin:

  lifecycle {
    ignore_changes = [
      disk,
    ]
  }

I tested removing the wwn manually and after that the terraform works without any issues, but I don't want to do this manually.

Is there any way to bypass this by a configuration parameter of the proxmox csi plugin or somehow to tell the plugin not add a wwn ? Changing providers is not an option for me at this point.

Logs

Nothing interesting in the logs of the Proxmox CSI Plugin components, only the error returned by terraform.

Environment

• Telmate/proxmox terraform provider
• Plugin version: v0.14.0
• Kubernetes version: v1.31.2
• OS version Debian 12 on the worker node

[sergelogvinov]

Hello, the wwm parameter is very important for the CSI plugin.

The CSI plugin mutates the VM configuration to attach or detach block devices (disks). Terraform also manages the VM configuration and may revert the changes made by the CSI plugin. To use both solutions together, you need to instruct Terraform to ignore all disks on the VM after creating.

I gave up on using the Telmate/proxmox provider because I encountered many issues with unpredictable disk behavior on VMs.
I recommend considering bpg/terraform-provider-proxmox - it’s well-maintained and feature-rich.