When create_vm_from_cloud_init raises after the VMID was allocated (failed disk import, failed start, …), the half-built VM stays on the hypervisor and the exception carries no VMID, so the caller can't remove it. netOrk now removes the VM of a failed job (NetOrk/netork#1141), but only when it got the id back.
Fix: clean up inside the driver on failure, or attach the vmid/node to the exception.
Prio P4.
When `create_vm_from_cloud_init` raises after the VMID was allocated (failed disk import, failed start, …), the half-built VM stays on the hypervisor and the exception carries no VMID, so the caller can't remove it. netOrk now removes the VM of a failed job (NetOrk/netork#1141), but only when it got the id back.
**Fix:** clean up inside the driver on failure, or attach the vmid/node to the exception.
**Prio P4.**
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When
create_vm_from_cloud_initraises after the VMID was allocated (failed disk import, failed start, …), the half-built VM stays on the hypervisor and the exception carries no VMID, so the caller can't remove it. netOrk now removes the VM of a failed job (NetOrk/netork#1141), but only when it got the id back.Fix: clean up inside the driver on failure, or attach the vmid/node to the exception.
Prio P4.