Create a template got timeout

[kaltsi]

During the template creation I got lock error.
Task viewer: VM 120 - Convert to template
trying to acquire lock...
TASK ERROR: can't lock file '/var/lock/pve-manager/pve-storage-local' - got timeout
But the service convert to template the VM, it means the configuration of VM increased with 'template: 1'.
But the disk is staid in 'vm-'. That's why this template will not be clonable.
The service point of view it is a bug. Because it can only be converted back to VM manually.

 

[oguz]

hi,

can you post the configuration of the VM? please run qm config VMID and post the output here, along with your pveversion -v

 

[kaltsi]

~$ pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.4: 6.4-6
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.4.140-1-pve: 5.4.140-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksmtuned: 4.20150326
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-9
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-11
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.10-1
proxmox-backup-file-restore: 2.0.10-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-3
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-14
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

qm config 120
boot: order=virtio0;net0
bootdisk: virtio0
cores: 2
cpu: host
memory: 6144
name: Template-ND20-v1.5-BD01
net0: virtio=F2:4F:DF:D1:B8:B7,bridge=vmbr0
net1: virtio=A6:ED:9B:B8:AB:A6,bridge=vmbr0
net2: virtio=16:40:83:98:AF:3E,bridge=vmbr0
numa: 0
ostype: l26
scsihw: virtio-scsi-single
smbios1: uuid=d929cf9c-c6e3-48af-92b5-8ba9663ab738
sockets: 3
template: 1
virtio0: local:120/vm-120-disk-0.qcow2,cache=writeback,size=1G
vmgenid: 30886031-de79-4d97-ad06-6b5edced677a

Here you are.

 

[oguz]

that's weird.

do you have space? what do you get from pvesm status

could you try removing the template: 1 from the config file and try converting to template again using the GUI?

 

[kaltsi]

pvesm status
Name         Type     Status           Total            Used       Available        %
local         dir     active       308587328       142952244       149890060   46.32%

As I know the conversion only renames the file and sets the permission to read only.
I did it. I removed the template line and got right result.
Maybe it happens during parallel activities.

But it is very similar situation when I created VM via API interface with "template=1" attribute. The system is accepted it, But the created template will be unusable from the same reason. In this case the system why accept the request, or why the system doesn't create 'base' disk.

 

[oguz]

I did it. I removed the template line and got right result.
Maybe it happens during parallel activities.

so now it worked when you tried to convert it to template?

But it is very similar situation when I created VM via API interface with "template=1" attribute. The system is accepted it, But the created template will be unusable from the same reason. In this case the system why accept the request, or why the system doesn't create 'base' disk.

for that you can create the vm normally and then convert it with qm template VMID

 

[kaltsi]

Yes the second try worked perfectly.

The problem is that, during the conversion there is a timeout problem due to a storage lock, the VM will be Template but the disk not.