public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: "Michael Köppl" <m.koeppl@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH container v9 06/10] add linked clone check when destroying container template
Date: Tue, 30 Jun 2026 15:57:03 +0200	[thread overview]
Message-ID: <cb4c9fba-bdc0-43d9-a7d8-5ffd998fe312@proxmox.com> (raw)
In-Reply-To: <20260629140439.184878-7-m.koeppl@proxmox.com>

Am 29.06.26 um 4:04 PM schrieb Michael Köppl:
> This check matches the behavior already implemented for VMs and prevents
> partial storage deletion if a container template has a linked clone. In
> such cases, the destruction of the container template will now fail,
> informing the user that the base volume is still in use by the linked
> clone. In case of a storage error (such as the underlying storage no
> existing anymore), a warning will be printed and execution continues,
> mimicking the handling of storage errors in later stages of
> destroy_lxc_container().
> 
> Originally-by: Stefan Hrdlicka <s.hrdlicka@proxmox.com>
>  [ MK: use classify_mountpoint instead of pattern matching
>        display warning for storage errors during linked clone check
>        resolve style nit ]
> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
> ---
>  src/PVE/LXC.pm | 19 +++++++++++++++++++
>  1 file changed, 19 insertions(+)
> 
> diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
> index e76da29f..c9f3cba7 100644
> --- a/src/PVE/LXC.pm
> +++ b/src/PVE/LXC.pm
> @@ -1024,6 +1024,25 @@ sub destroy_lxc_container {
>      my ($storage_cfg, $vmid, $conf, $replacement_conf, $purge_unreferenced) = @_;
>  
>      my $volids = {};
> +
> +    if ($conf->{template}) {
> +        PVE::LXC::Config->foreach_volume_full(
> +            $conf,
> +            { include_unused => 1 },
> +            sub {
> +                my ($ms, $mountpoint) = @_;
> +                my $volid = $mountpoint->{volume};
> +                return if !$volid || PVE::LXC::Config->classify_mountpoint($volid) ne 'volume';
> +                my $result =
> +                    eval { PVE::Storage::volume_is_base_and_used($storage_cfg, $volid) };
> +                PVE::RESTEnvironment::log_warn(
> +                    "failed to check if volume '$volid' is used by linked clones: $@")
> +                    if $@;

Style nit: multi-line post-if. If you import the log_warn() directly, it
should be shorter ;)

Maybe note with a comment that this is an early check and removal of the
volume itself would still fail later, which is why it's fine to just log
a warning here.

> +                die "base volume '$volid' is still in use by linked clone\n" if $result;
> +            },
> +        );
> +    }
> +
>      my $remove_volume = sub {
>          my ($ms, $mountpoint) = @_;
>  





  reply	other threads:[~2026-06-30 13:57 UTC|newest]

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

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=cb4c9fba-bdc0-43d9-a7d8-5ffd998fe312@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal