Error: 500 CT 241 already running, v3.0.1-rc5

[AobaIwaki123]

Abstract

I faced an Error Error: 500 CT 241 already running when I create Proxmox LXC with version v3.0.1-rc5
After terraform apply, I got this error but Proxmox LXC is working properly.
So, I guess health check system is something wrong.
And also, I can not do terraform destroy on this LXC for some reason.
It's really inconvenient. I'm really grad if it's fixed

Checked

• v3.0.1-rc4 does not have this issue
• If start=false, I can not see this issue. I can do terraform apply and terraform destroy
• v3.0.1-rc6 has same issue

Full Error Log

module.proxmox_lxc.proxmox_lxc.basic: Creating...
module.proxmox_lxc.proxmox_lxc.basic: Still creating... [10s elapsed]

│ Error: 500 CT 241 already running
│ 
│   with module.proxmox_lxc.proxmox_lxc.basic,
│   on ../../modules/proxmox_lxc/main.tf line 1, in resource "proxmox_lxc" "basic":
│    1: resource "proxmox_lxc" "basic" {

Environment

Here's my environment
If you need more info, please tell me.

• Ubuntu: 24.10
• Terraform: v1.9.8
• tfenv: 3.0.0
• Proxmox: 8.3.0
• proxmox provider: 3.0.1-rc5

My Proxmox LXC Module

resource "proxmox_lxc" "basic" {
  features {
      nesting = true
  }
  
  vmid = var.vmid
  target_node  = var.target_node
  hostname     = var.hostname
  ssh_public_keys = var.public_key

  ostemplate   = "local:vztmpl/${var.template}.tar.zst"

  cores  = var.cores
  memory = var.memory

  unprivileged = true
  start       = true

  // Terraform will crash without rootfs defined
  rootfs {
    storage = var.storage
    size    = "${var.disk_size}G"
  }

    network {
        name = "eth0"
        bridge = var.bridge
        ip = "${var.ip_address}/24"
        gw = var.gateway
    }
}

[AobaIwaki123]

I could not see this issue on 3.0.1-rc6. So, I close this issue

[AobaIwaki123]

Sorry I did not update provider version from rc4 and I found same issue on rc6.
So, I reopen this issue

[sulaimanzai]

I also face the same issue! on rc6.

[sulaimanzai]

if comment out these in my container config then no error.

# start = true
# onboot = true

but i want to start the container so thats when the error occurs.

[sulaimanzai]

onboot = true, suppose to turn on the container but it did not during boot.

[sulaimanzai]

resource "proxmox_lxc" "wireguard" { 
    target_node  = "pve"
    hostname = "wireguard"
    onboot = true
   # start = true
    cores = 1
    memory = "1024"
    swap = "2048"
    nameserver = "8.8.8.8"
    network {
        name = "eth0"
        bridge = "vmbr0"
        ip = "192.168.43.10/32"  
        gw = "192.168.43.1"
        firewall = true
    }
    ostemplate = "local:vztmpl/debian-12-standard_12.7-1_amd64.tar.zst" 
    password = var.linux_password
    rootfs {
        storage = "local-lvm"
        size = "8G"
    }
    unprivileged = true
    ssh_public_keys = var.sshkey
}

[AobaIwaki123]

Checked

• v3.0.1-rc4 does not have this issue
• If start=false, I can not see this issue. I can do terraform apply and terraform destroy
• v3.0.1-rc6 has same issue

As I mentioned here, this issue is appeared on rc5 and rc6.
So, I'm using rc4 to avoid this issue

[bchards]

Also experiencing the same issue with v3.0.1-rc6 - switching to rc4 fixes the issue for now as mentioned.

[bdruth]

This is happening to me, too. Tracked down the change to this PR #1093

Thoughts @Sonlis? This change is in rc5 and rc6, which matches the observations above.

[Sonlis]

I unfortunately do not have access to a proxmox instance for the next 2 weeks, so I cannot reproduce it. I checked the code though and came up with an idea of why it would fail. I think this block of code is useless:

terraform-provider-proxmox/proxmox/resource_lxc.go

Line 592 in 7e66709

if d.Get("start").(bool) {

, starting or not the LXC is already contained in the config when the LXC is created:

terraform-provider-proxmox/proxmox/resource_lxc.go

Line 660 in 7e66709

config.Start = d.Get("start").(bool)

Now, I created the PR because the LXC would not start even when setting the boolean, and when running it locally it worked and actually started the LXC. I did not test extensively and actually didn't see that the start boolean is already set in the config. It shouldn't have to try again to start the LXC once it's created, which would explain the error of trying to start an already started LXC.

Again, I cannot affirm 100% that this is the problem until I have access to my proxmox again.

[deakus]

I also confirm the same issue using proxmox 8.3.2 with Terrform v1.10.3 and provider /telmate/proxmox v3.0.1-rc6

[bluescountry]

i have same issue

[gilkudik]

I'm having the same issue.

Maybe following this it can be fixed.