From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Jakob Klocker <j.klocker@proxmox.com>
Subject: applied: [PATCH container] fix: #7148: check CT protection before reassigning volume
Date: Wed, 26 Aug 2026 16:16:35 +0200 [thread overview]
Message-ID: <178775379009.210123.1931139643106353439.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260601115240.36497-1-j.klocker@proxmox.com>
On Mon, 01 Jun 2026 13:52:40 +0200, Jakob Klocker wrote:
> When reassigning a volume, check the destination config before
> removing the volume from the source config.
Applied, thanks! Ran make tidy, extended the commit message a bit and
avoided the misleading "volume '$target_mpkey'" in the error message,
which wrongly uses the target mp id, while making it fully explicit
that the assignment to the target is what fails because of the
protection mode.
[1/1] fix: #7148: check CT protection before reassigning volume
commit: c05243e426f69abc06a5768cafdbca3934f6caa4
prev parent reply other threads:[~2026-08-26 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 11:52 [PATCH container] fix: #7148: check CT protection before reassigning volume Jakob Klocker
2026-06-05 14:26 ` Lukas Sichert
2026-08-26 14:22 ` Fiona Ebner
2026-08-26 14:16 ` 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=178775379009.210123.1931139643106353439.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=j.klocker@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.