From: Elias Huhsovitz <e.huhsovitz@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Elias Huhsovitz <e.huhsovitz@proxmox.com>
Subject: [PATCH manager 0/2] fix #7860: api: pool: do not delete when used by backup job
Date: Wed, 30 Sep 2026 16:51:41 +0200 [thread overview]
Message-ID: <20260930145143.210066-1-e.huhsovitz@proxmox.com> (raw)
Deleting a pool that is still used by a backup job leaves the job in
an invalid state. DELETE `/cluster/backup-info/not-backed-up` then
fails with "pool '<name>' does not exist", which causes the GUI to
hide the "Show guests without backup job" button (bug #7860).
This small series aims to prevent the invalid configuration state.
Summary of changes
------------------
Elias Huhsovitz (2):
fix #7860: api: pool: do not delete when used by backup job
api: pool: update delete enpoint description to match behaviour
PVE/API2/Pool.pm | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
--
2.47.3
next reply other threads:[~2026-09-30 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 14:51 Elias Huhsovitz [this message]
2026-09-30 14:51 ` [PATCH manager 1/2] fix #7860: api: pool: do not delete when used by backup job Elias Huhsovitz
2026-09-30 14:51 ` [PATCH manager 2/2] api: pool: update delete enpoint description to match behaviour Elias Huhsovitz
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=20260930145143.210066-1-e.huhsovitz@proxmox.com \
--to=e.huhsovitz@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.