From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server v2 2/4] agent: treat freeze-fs-on-backup as alias for guest-fsfreeze
Date: Fri, 27 Mar 2026 00:05:15 +0100 [thread overview]
Message-ID: <a1c7a04e-c354-49d4-9578-7d841ec1598c@proxmox.com> (raw)
In-Reply-To: <2dea817d-e523-4036-aad7-f1b7543bf3f2@proxmox.com>
Am 26.03.26 um 13:55 schrieb Fiona Ebner:
> Am 25.03.26 um 10:34 PM schrieb Thomas Lamprecht:
>> Alias the deprecated key to 'guest-fsfreeze' through the JSONSchema
>> alias key support so consumers see a single, consistent value.
>> Previously only the backup code path fell back to it, while snapshots,
>> replications, clones and imports silently ignored it.
>>
>> Note that while alias support for top-level JSON schema has a bug [0],
>> the one for property strings - which this here is - works out fine.
>>
>> [0]: https://lore.proxmox.com/all/20251205100317.1101549-1-d.csapak@proxmox.com/
>>
>> The key stays in the schema indefinitely for old backup restore
>> compatibility rather than being removed in a future major release.
>>
>
> One potentially surprising thing (I guess another bug in JSONSchema?) is
> that it's possible to set
> qm set 100 --agent 1,freeze-fs=0,freeze-fs-on-backup=1
> and the second option (which in this case is the deprecated one) will
> then override the first when parsing. The check for duplicate keys
> precedes the resolution of the alias in parse_property_string():
>
> https://git.proxmox.com/?p=pve-common.git;a=blob;f=src/PVE/JSONSchema.pm;h=17e7126a6c42f8326a1da890680af10b6106d906;hb=17c6c3bdcf018756b4b48589b5485663103a9843#l1069
Ah, right, that pre-existing issue should be fixed in latest pve-common [0].
[0]: https://git.proxmox.com/?p=pve-common.git;a=commitdiff;h=5d843877321a69255dd55b49cd1c8e13222dd914
next prev parent reply other threads:[~2026-03-26 23:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 21:28 [PATCH qemu-server v2 0/4] rework fs-freeze agent property Thomas Lamprecht
2026-03-25 21:28 ` [PATCH qemu-server v2 1/4] agent: add should_fs_freeze helper Thomas Lamprecht
2026-03-26 12:55 ` Fiona Ebner
2026-03-27 1:12 ` Thomas Lamprecht
2026-03-25 21:28 ` [PATCH qemu-server v2 2/4] agent: treat freeze-fs-on-backup as alias for guest-fsfreeze Thomas Lamprecht
2026-03-26 12:55 ` Fiona Ebner
2026-03-26 23:05 ` Thomas Lamprecht [this message]
2026-03-27 8:53 ` Fiona Ebner
2026-03-25 21:28 ` [PATCH qemu-server v2 3/4] tests: cfg2cmd: add agent guest-fsfreeze config tests Thomas Lamprecht
2026-03-26 12:55 ` Fiona Ebner
2026-03-25 21:28 ` [PATCH qemu-server v2 4/4] qga: rename guest-fsfreeze to freeze-fs Thomas Lamprecht
2026-03-26 9:08 ` Maximiliano Sandoval
2026-03-26 21:46 ` Thomas Lamprecht
2026-03-26 12:55 ` Fiona Ebner
2026-03-26 23:16 ` applied: [PATCH qemu-server v2 0/4] rework fs-freeze agent property 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=a1c7a04e-c354-49d4-9578-7d841ec1598c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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