From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH-SERIES storage/manager 0/4] fix #8169: backup: extract config: fix regression with backup type check
Date: Mon, 19 Oct 2026 12:57:51 +0200 [thread overview]
Message-ID: <20261019110029.92256-1-f.ebner@proxmox.com> (raw)
Allow a user with Datastore.Allocate to extract the configuration from
a guest backup. Avoid early checks for the backup's associated guest
ID, because not all guest backups have one. Extracting the
configuration from an ID-less guest backup regressed and this fixes
the regression. The storage layer already checks for the backup's
type.
storage:
Fiona Ebner (2):
pvesm: extractconfig: allow access for Datastore.Allocate
fix #8169: pvesm: extractconfig: fix regression with backup type check
src/PVE/CLI/pvesm.pm | 8 --------
1 file changed, 8 deletions(-)
manager:
Fiona Ebner (2):
api: backup: extract config: allow access for Datastore.Allocate
fix #8169: api: backup: extract config: fix regression with backup
type check
PVE/API2/VZDump.pm | 8 --------
1 file changed, 8 deletions(-)
Summary over all repositories:
2 files changed, 0 insertions(+), 16 deletions(-)
--
Generated by git-murpp 0.5.0
next reply other threads:[~2026-10-19 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 10:57 Fiona Ebner [this message]
2026-10-19 10:57 ` [PATCH storage 1/4] pvesm: extractconfig: allow access for Datastore.Allocate Fiona Ebner
2026-10-19 10:57 ` [PATCH storage 2/4] fix #8169: pvesm: extractconfig: fix regression with backup type check Fiona Ebner
2026-10-19 10:57 ` [PATCH manager 3/4] api: backup: extract config: allow access for Datastore.Allocate Fiona Ebner
2026-10-19 10:57 ` [PATCH manager 4/4] fix #8169: api: backup: extract config: fix regression with backup type check Fiona Ebner
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=20261019110029.92256-1-f.ebner@proxmox.com \
--to=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 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.