[SOLVED] Can't start VM - CloudInit - ISCSI LVM

[alaintno]

Hello,

I have a 4 nodes cluster, sharing an ISCSI LUN with LVM on top of it.

I've created a template that I use to clone VM and add a cloudinit drive.

Everything works fine until I stop the VM (which has it's disk and clouinit on the shared LVM), it then complains that it cannot start :

Use of uninitialized value in split at /usr/share/perl5/PVE/QemuServer/Cloudinit.pm line 96.

qemu-img: Could not open '/dev/prd/vm-106-cloudinit': Could not open '/dev/prd/vm-106-cloudinit': No such file or directory
TASK ERROR: error with cfs lock 'storage-rkg-lvm-prd': lvcreate 'prd/pve-vm-106' error:   Logical Volume "vm-106-cloudinit" already exists in volume group "prd"

I remove and recreate the cloudinit drive, and the VM is able to start normally.

I there a way to make this work every time, without removing and recreating the cloudinit drive ?

Thanks.

For information :

pve-cluster    5.0-37
pve-container    2.0-39
pve-docs    5.4-2
pve-edk2-firmware    1.20190312-1
pve-firewall    3.0-21
pve-firmware    2.0-6
pve-ha-manager    2.0-9
pve-i18n    1.1-4
pve-kernel-4.15    5.4-2
pve-kernel-4.15.18-14-pve    4.15.18-39
pve-libspice-server1    0.14.1-2
pve-manager    5.4-6
pve-qemu-kvm    3.0.1-2
pve-xtermjs    3.12.0-1

 

[mira]

Please post the complete output of 'pveversion -v'.
But this sounds like you're not using the current qemu-server version. Please update.

 

[alaintno]

Here it is :

pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-14-pve)
pve-manager: 5.4-6 (running version: 5.4-6/aa7856c5)
pve-kernel-4.15: 5.4-2
pve-kernel-4.15.18-14-pve: 4.15.18-39
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-10
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-52
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-43
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-37
pve-container: 2.0-39
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-21
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-2
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-51
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3

 

[alaintno]

You were right. I've updated the four nodes. And now the VM can start with no errors.

Thanks !