From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pve-devel] [PATCH stable-7 guest-common] storage tunnel: correctly set disk-import parameters
Date: Tue, 4 Mar 2025 19:09:40 +0100 [thread overview]
Message-ID: <59c810a7-6e46-45de-aaf3-718b8c7c38b4@proxmox.com> (raw)
In-Reply-To: <1739357696.r0x5a3ncuw.astroid@yuna.none>
Am 12.02.25 um 11:55 schrieb Fabian Grünbichler:
> do we still want to bump this? do we also want to include other recent
> fixes for remote migration if we do so?
Not a huge fan, but it would be fine for me as long as they are
targeted; ensuring upgrade is easy reduces pressure for requiring an
LTS.
> On November 29, 2024 12:54 pm, Fiona Ebner wrote:
>> From: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>>
>> according to the schema, else some combinations of migration / guest /
>> storage settings will fail validation:
>>
>> 2024-05-15 11:48:51 ERROR: migration_snapshot: type check ('boolean') failed - got ''
>>
>> since this is client / source side, remote migrations to a remote node
>> with validation enabled can fail without this change.
>>
>> The fact that this is required for Proxmox VE 7 was reported in the
>> community forum:
>> https://forum.proxmox.com/threads/158202/
>>
>> While Proxmox VE 7 is end-of-life since the end of July 2024, it's
>> still nice to keep upgrade paths to supported versions open.
Albeit remote migration was/is rather a bit experimental in general,
but as mentioned above I agree in general with the sentiment.
>>
>> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>> Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
>> (cherry picked from commit 172ab9f5ccc40666478f2f83696e6b1e62090e2a)
>> [FE: add rationale for backport]
>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>> ---
>> src/PVE/StorageTunnel.pm | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-03-04 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 11:54 Fiona Ebner
2025-02-12 10:55 ` Fabian Grünbichler
2025-03-04 18:09 ` Thomas Lamprecht [this message]
2025-03-05 9:46 ` Fiona Ebner
2025-03-05 11:12 ` Thomas Lamprecht
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=59c810a7-6e46-45de-aaf3-718b8c7c38b4@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@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.