From: "Jean-Léon CUSINATO" <jlcusinato@neverhack.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Cc: "Olivier GESNY" <ogesny@neverhack.com>,
"Loïc SCOTTO DI PERROTOLO" <lscottodiperrotolo@neverhack.com>
Subject: bug #7864: pool-scoped VM create with tags still broken. Could someone pick up the patch?
Date: Fri, 21 Aug 2026 08:29:40 +0000 [thread overview]
Message-ID: <MR1PPF2CB85BE05FA52B10B00800CCC9ED5C0A32@MR1PPF2CB85BE05.FRAP264.PROD.OUTLOOK.COM> (raw)
Hi,
I would like to raise some attention on bug #7864, which looks ready to be
applied but seems to have stalled:
https://bugzilla.proxmox.com/show_bug.cgi?id=7864
Since 9.2, a user or API token whose privileges come only from
/pool/<pool> gets a 403 as soon as --tags is passed to VM create.
The reporter attached three patches on 2026-07-30 and Fabian confirmed the
next day that the analysis and fix look correct, pointing at the Developer
Documentation for submission. Nothing seems to have reached this list
since, and pve-guest-common master don't have the patch applied,
so I suspect the CLA step is where it stopped.
I am a user rather than a Perl developer, so I am not really in a position
to produce a good series myself. Would one of you be willing to pick this
up? The change looks small and the review appears to already be done. I am
glad to test any patch against a pool-scoped token and report back.
If nobody has the time for it, tell me and I will make an attempt, but I
would rather not be the one writing Perl for a permission check.
Respectfully,
Jean-Léon CUSINATO
reply other threads:[~2026-08-21 8:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=MR1PPF2CB85BE05FA52B10B00800CCC9ED5C0A32@MR1PPF2CB85BE05.FRAP264.PROD.OUTLOOK.COM \
--to=jlcusinato@neverhack.com \
--cc=lscottodiperrotolo@neverhack.com \
--cc=ogesny@neverhack.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.