[Bug]: Error when updating a load balancer: provider produced an unexpected new value: Root object was present, but now absent.

[chrisi]

What happened?

Terraform will perform the following actions:

  # module.kube-hetzner.hcloud_load_balancer_network.cluster[0] will be created
  + resource "hcloud_load_balancer_network" "cluster" {
      + enable_public_interface = true
      + id                      = (known after apply)
      + ip                      = (known after apply)
      + load_balancer_id        = 2455606
      + subnet_id               = "10902552-10.0.0.0/16"
    }

  # module.kube-hetzner.hcloud_load_balancer_target.cluster[0] will be created
  + resource "hcloud_load_balancer_target" "cluster" {
      + id               = (known after apply)
      + label_selector   = "cluster=k3s-dev,engine=k3s,provisioner=terraform,role in (control_plane_node,agent_node)"
      + load_balancer_id = 2455606
      + type             = "label_selector"
      + use_private_ip   = true
    }

Plan: 2 to add, 0 to change, 0 to destroy.
module.kube-hetzner.hcloud_load_balancer_network.cluster[0]: Creating...
╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to module.kube-hetzner.hcloud_load_balancer_network.cluster[0], provider "provider[\"registry.terraform.io/hetznercloud/hcloud\"]" 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:

create project on https://console.hetzner.com/, create api-token.

tmp_script=$(mktemp) && curl -sSL -o "${tmp_script}" https://raw.githubusercontent.com/kube-hetzner/terraform-hcloud-kube-hetzner/master/scripts/create.sh && chmod +x "${tmp_script}" && "${tmp_script}" && rm "${tmp_script}"

follow onscreen instructions.

edit kube.tf, enter api-token etc.

hcloud-provider: 1.49.1
terraform-hcloud-kube-hetzner: 2.17.0

terraform init
terraform apply --auto-approve

edit kube.tf again (for example add some nodes)

hcloud-provider: 1.52.0
terraform-hcloud-kube-hetzner: 2.17.3

terraform init --upgrade
terraform apply --auto-approve

What did you expect to happen?

I expect the apply-command to produce no errors.

Please provide a minimal working example

n/a