terraform-provider-proxmox: 4 vm creation - all get the same id and it fails. new version "3.0.1-rc4"
Tring to create 4 machines. Terraform apply try to create all 4 with the same id and it fails:
Simple example, there is also a second part of the “loop” to create other two machines.
resource "proxmox_vm_qemu" "cloudinit-k3s-master" {
# Node name has to be the same name as within the cluster
# this might not include the FQDN
target_node = "home"
desc = "Cloudinit Ubuntu"
count = 2
onboot = true
# The template name to clone this vm from
clone = "ubuntu-cloud"
# Activate QEMU agent for this VM
agent = 0
os_type = "cloud-init"
cores = 2
sockets = 2
numa = true
vcpus = 0
cpu = "host"
memory = 2048
name = "k3s-master-0${count.index + 1}"
#cloudinit_cdrom_storage = "local-lvm"
scsihw = "virtio-scsi-pci"
bootdisk = "scsi0"
boot = "order=scsi0;ide2"
disks {
ide {
ide2 {
cloudinit {
storage = "local-lvm"
}
}
}
scsi {
scsi0 {
disk {
size = "22732M"
#cache = "writeback"
storage = "local-lvm"
#storage_type = "rbd"
#iothread = true
#discard = true
}
}
}
}
# Setup the ip address using cloud-init.
# Keep in mind to use the CIDR notation for the ip.
ipconfig0 = "ip=192.x${count.index + 1}/24,gw=192.x"
ciuser = "var.user"
nameserver = "192.x"
sshkeys = var.ssh
}
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 20
Commits related to this issue
- add warning related to #1136 — committed to Tinyblargon/terraform-provider-proxmox by Tinyblargon 2 years ago
Got into the same issue, currently running with
I know this slows down the whole process since its not running anything in parallel any more, but at least it is usable until this has been fixed.
The next release [3.0.1-rc7] will mostly resolve this treading issue.
@zapotocnylubos Yes, when running parralel deployments (multiple parralel terraform apply), you should handle the ID. When running, just one terraform apply over multiple threads the provider should be able to handle it (due to an implementation issue it can’t).
To fix the treading for 1 terraform apply, some changes have to be made in
proxmox-api-goand in this project (I’m already working on those).It’s also possible to deal with the multiple parralel providers in
proxmox-api-go, but that would be a lot of work and isn’t a blocker for the official 3.0 release.@zapotocnylubos running multiple terraforms in parralel is always going to be an issue. As we can only have a lock in terraform or the client session. In your specific use case, I’d look into assigning a specific id to each vm.
@zuka1337 for now the solution is what @hayer suggests. The treading at the core of the provider needs to be reworked.
Probably best for now to make
pm_parralleldefault to1, and put a warning in the description that setting it higher causes issues in certain scenarios.