Package: libvirt-daemon Version: 7.0.0-3 Severity: important Dear Maintainer,
I cannot create a LVM volume if there is an existing signature on that device. This happen while trying to clone a VM or to create a new VM. This bug has been comfirmed (https://bugzilla.redhat.com/show_bug.cgi?id=1940413) and patched on upstream version 7.6 (https://gitlab.com/libvirt/libvirt/-/commit/d91a3e96c04ae093f4422b52e259750c86ba79fc). I was unsure whether I should fill a bug report in order to backport a fix to stable. A workaround is to run the lvcreate command manually. But it is a nightmare when cloning a VM, as you need to create the new volume to wipe it, and remove it to clone the orignal disk. -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libvirt-daemon depends on: ii libblkid1 2.36.1-8 ii libc6 2.31-13 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgcc-s1 10.2.1-6 ii libglib2.0-0 2.66.8-1 ii libnetcf1 1:0.2.8-1.1 ii libparted2 3.4-1 ii libpcap0.8 1.10.0-2 ii libpciaccess0 0.16-1 ii libselinux1 3.1-3 ii libudev1 247.3-6 ii libvirt-daemon-driver-qemu 7.0.0-3 ii libvirt0 7.0.0-3 ii libxml2 2.9.10+dfsg-6.7 Versions of packages libvirt-daemon recommends: ii libvirt-daemon-driver-lxc 7.0.0-3 ii libvirt-daemon-driver-vbox 7.0.0-3 ii libvirt-daemon-driver-xen 7.0.0-3 ii libxml2-utils 2.9.10+dfsg-6.7 ii netcat-openbsd 1.217-3 ii qemu-system-x86 [qemu-kvm] 1:5.2+dfsg-11 Versions of packages libvirt-daemon suggests: pn libvirt-daemon-driver-storage-gluster <none> pn libvirt-daemon-driver-storage-iscsi-direct <none> pn libvirt-daemon-driver-storage-rbd <none> pn libvirt-daemon-driver-storage-zfs <none> ii libvirt-daemon-system 7.0.0-3 pn numad <none> -- no debconf information