all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, "Michael Köppl" <m.koeppl@proxmox.com>
Subject: applied: [PATCH container/qemu-server v10 00/10] fix #3711 and adapt drive detach/remove behavior
Date: Fri,  3 Jul 2026 14:44:52 +0200	[thread overview]
Message-ID: <178308237298.133234.6445363936266889934.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260701141339.181276-1-m.koeppl@proxmox.com>

On Wed, 01 Jul 2026 16:13:29 +0200, Michael Köppl wrote:
> This series aims to fix #3711 [0] and streamline the detach/remove
> behavior around volumes that are either mounted into a container or
> attached to a VM as a hard disk. It also adds warnings in case a
> volume's underlying storage does not exist anymore. It is a
> continuation of a series from 2022 [1], but makes the following changes:
> 
> [...]

Applied, thanks! Changed one log message in each repo slightly to
clarify that the volume is removed from the config (and not from
somewhere else).

pve-container:

[01/10] fix #3711: warn about storage errors during mountpoint delete
        commit: 2b964d0f583dd585b06b09fb3025425093d4112a
[02/10] destroy_lxc, delete_mp_volume: rename $volume to $volid
        commit: a7b7505e9ba290f61f286d5d42937a881d94bf14
[03/10] config: ensure valid volid through parse_volume()
        commit: 613e12a9ea01dda6c8adb3ebd6e84720c69120f8
[04/10] lxc config: add helper for parsing volid and checking if storage exists
        commit: 032a73a73572704b58613f86899d9517b505f286
[05/10] allow pending mount point changes if storage is gone
        commit: 1f6c6dc307e84cd1e211a437e211ffd9ff2b8196
[06/10] destroy template: add early check for linked clones of volumes
        commit: ca9c3142962cc1e5d0045698d16481485fa1de16

qemu-server:

[07/10] adapt linked clone check to not die if an error occurs during check
        commit: 59e112351cca26f5d0e3f902752ece73193a25a7
[08/10] fix #3711: make removal of VM possible if store does not exist anymore
        commit: 2e85e6d7f4dd54f4bf8e9a6fbfb25bdb43f7683c
[09/10] destroy_vm: use log_warn for vdisk_free errors for consistency
        commit: 42e450dc03c3d05c4fbd1af9b32c678575c39a93
[10/10] display warnings for storage errors or if storage no longer exists
        commit: 5b5c576886fbbe79be52c977f9c7ba79a5bfa39f




      parent reply	other threads:[~2026-07-03 12:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 14:13 [PATCH container/qemu-server v10 00/10] fix #3711 and adapt drive detach/remove behavior Michael Köppl
2026-07-01 14:13 ` [PATCH container v10 01/10] fix #3711: warn about storage errors during mountpoint delete Michael Köppl
2026-07-01 14:13 ` [PATCH container v10 02/10] destroy_lxc, delete_mp_volume: rename $volume to $volid Michael Köppl
2026-07-01 14:13 ` [PATCH container v10 03/10] config: ensure valid volid through parse_volume() Michael Köppl
2026-07-01 14:13 ` [PATCH container v10 04/10] lxc config: add helper for parsing volid and checking if storage exists Michael Köppl
2026-07-01 14:13 ` [PATCH container v10 05/10] allow pending mount point changes if storage is gone Michael Köppl
2026-07-01 14:13 ` [PATCH container v10 06/10] destroy template: add early check for linked clones of volumes Michael Köppl
2026-07-01 14:13 ` [PATCH qemu-server v10 07/10] adapt linked clone check to not die if an error occurs during check Michael Köppl
2026-07-01 14:13 ` [PATCH qemu-server v10 08/10] fix #3711: make removal of VM possible if store does not exist anymore Michael Köppl
2026-07-01 14:13 ` [PATCH qemu-server v10 09/10] destroy_vm: use log_warn for vdisk_free errors for consistency Michael Köppl
2026-07-01 14:13 ` [PATCH qemu-server v10 10/10] display warnings for storage errors or if storage no longer exists Michael Köppl
2026-07-03 12:44 ` Fiona Ebner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178308237298.133234.6445363936266889934.b4-ty@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=m.koeppl@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal