Skip to main content
Question

Worker VM is deleted immediately – Cloud‑Init never runs – Proxmox Plug‑In Worker Bug?

Title: Worker VM is deleted immediately – Cloud‑Init never runs – Proxmox Plug‑In Worker Bug?

Description:

I am using Veeam Backup & Replication 13.x together with the Veeam Proxmox VE Plug‑In (version 3.x). The Worker Test always fails. The worker VM is created, receives a static IP (e.g. 192.168.0.28), but is deleted again after a few seconds — before Cloud‑Init or SSH ever start.

Symptoms:

  • Worker VM is created successfully

  • Static IP is injected by the Veeam Proxmox Proxy

  • VM boots for a few seconds

  • Cloud‑Init does not execute

  • SSH never comes up

  • Veeam aborts the worker initialization

  • VM is deleted immediately

  • Hookscript never runs (no stop event)

  • No logs appear on Proxmox because the VM is removed too early

Storage situation:

My worker storage is an LVM‑Thin pool (Data01):

Code

lvmthin: Data01
    thinpool Data01
    vgname Data01
    content rootdir,images
    nodes pve02

This storage type does not support ISO images or snippets. Cloud‑Init ISO cannot be created properly on this storage.

Network situation:

  • All other VMs on the same bridge (vmbr0) work perfectly

  • The worker VM receives its static IP correctly

  • Network is not the issue

Question:

  • Is this a known bug in the Veeam Proxmox Plug‑In (versions 1–3)?

  • Is there any plug‑in version where the worker initialization issue is fixed?

  • Does the worker VM require a storage that supports ISO images (e.g. local, NFS, CIFS)?

Additional note: The worker VM is deleted so quickly that Cloud‑Init and SSH never have a chance to initialize. This behavior seems identical to the known worker‑VM bug reported for the Proxmox plug‑in.

    1 comment

    Hallo here the information from worker test

     

    ✅ Testing the worker PVE02worker ✅ Finished searching for uploaded worker VM images ✅ The worker image was uploaded successfully ❌ Failed to deploy the worker VM: The power state of the VM 100 did not change to Stopped within the expected time period  |  0:12:47 ✅ The worker VM 6f1ac7ca‑27ed‑4b40‑b15e‑02fae3ed4f83:100 was removed from the cluster successfully  |  0:00:04 ❌ Worker PVE02worker test failed: The power state of the VM 100 did not change to Stopped within the expected time period

    That’s the full log text exactly as shown in your image.

    Terms & ConditionsAccessibility statement