We have a vm-template that was created by choosing "convert to template".
However the migration of this template fails with the following error:
Indeed this template's disk was renamed automatically from vm-111-disk-1 to base-111-disk-1 when it converted to a template.
My workaround to migrate this template for now is to do a Full Clone and then migrate the clone, and then convert it to a template again (it will then rename the vm-149-disk-1 to base-149-disk-1 again and make migration impossible).
It this a known bug? We use Proxmox 5.1 on ext4 disks.
Looking at https://git.proxmox.com/?p=pve-storage.git;a=blob;f=PVE/Storage/DRBDPlugin.pm#l174 it also should allow a match on ^base-$vmid- ?
However the migration of this template fails with the following error:
Code:
2018-01-06 13:08:54 found local disk 'local-lvm:base-111-disk-1' (in current VM config)
2018-01-06 13:08:54 copying disk images
illegal name 'base-111-disk-1' - sould be 'vm-111-*'
dd: error writing 'standard output': Connection reset by peer
14+0 records in
13+0 records out
903552 bytes (904 kB, 882 KiB) copied, 0.422384 s, 2.1 MB/s
command 'dd 'if=/dev/pve/base-111-disk-1' 'bs=64k'' failed: exit code 1
exit code 255
send/receive failed, cleaning up snapshot(s)..
2018-01-06 13:08:56 ERROR: Failed to sync data - command 'set -o pipefail && pvesm export local-lvm:base-111-disk-1 raw+size - -with-snapshots 0' failed: exit code 1
2018-01-06 13:08:56 aborting phase 1 - cleanup resources
2018-01-06 13:08:56 ERROR: found stale volume copy 'local-lvm:base-111-disk-1' on node 'fe-prodsup10'
2018-01-06 13:08:56 ERROR: migration aborted (duration 00:00:03): Failed to sync data - command 'set -o pipefail && pvesm export local-lvm:base-111-disk-1 raw+size - -with-snapshots 0' failed: exit code 1
TASK ERROR: migration abortedIndeed this template's disk was renamed automatically from vm-111-disk-1 to base-111-disk-1 when it converted to a template.
My workaround to migrate this template for now is to do a Full Clone and then migrate the clone, and then convert it to a template again (it will then rename the vm-149-disk-1 to base-149-disk-1 again and make migration impossible).
It this a known bug? We use Proxmox 5.1 on ext4 disks.
Looking at https://git.proxmox.com/?p=pve-storage.git;a=blob;f=PVE/Storage/DRBDPlugin.pm#l174 it also should allow a match on ^base-$vmid- ?
Code:
proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)
pve-manager: 5.1-41 (running version: 5.1-41/0b958203)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.13.13-2-pve: 4.13.13-32
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-18
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9
openvswitch-switch: not correctly installed