1 files changed, 0 insertions, 19 deletions

diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/2039.toml b/gitlab/issues/target_missing/host_missing/accel_missing/2039.toml
deleted file mode 100644
index 29a18e581..000000000
--- a/gitlab/issues/target_missing/host_missing/accel_missing/2039.toml
+++ /dev/null
@@ -1,19 +0,0 @@
-id = 2039
-title = "there is no 'write' lock checked when exec `qemu-img check lvqcow2`"
-state = "opened"
-created_at = "2023-12-18T06:35:03.135Z"
-closed_at = "n/a"
-labels = ["Storage", "workflow::Needs Info"]
-url = "https://gitlab.com/qemu-project/qemu/-/issues/2039"
-host-os = "- OS/kernel version:"
-host-arch = "- QEMU flavor:"
-qemu-version = "- QEMU command line:"
-guest-os = "- OS/kernel version:"
-guest-arch = "## Description of problem"
-description = """There is a difference between a qcow2 file image and a lvqcow2 img.
-
-'write' lock will be checked when using a normal qcow2-format image (/path/to/img/test.qcow2) to avoid some risky operations. However, when I create a qcow2 img on a lv, there is not any write lock checked when I perform `qemu-img check` on this lvqcow2 even though it was attached to a vm."""
-reproduce = """1. create a lvqcow2: `qemu-img create -f qcow2 /path/to/lv  xxG`
-2. create a vm using this lvqcow2
-3. exec `qemu-img check` on this lvqcow2, there is no any perm (such as 'write' lock) check and notifaction even though this lvqcow2 is using in qemu vm."""
-additional = """"""