From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com,
Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
Subject: applied: [PATCH pve-storage v2 1/1] fix #7077: lvm: Improve ID verification error messages
Date: Mon, 21 Sep 2026 14:34:27 +0200 [thread overview]
Message-ID: <178999406150.173954.11638196010192324859.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260206161236.335026-5-a.bied-charreton@proxmox.com>
On Fri, 06 Feb 2026 17:12:35 +0100, Arthur Bied-Charreton wrote:
> The regex in Storage::parse_lvm_name has an implicit `length >= 2`
> constraint, and shorter IDs failed with "contains illegal characters".
> Add explicit length check to return a clearer error message in this case.
Applied, thanks!
[1/1] fix #7077: lvm: Improve ID verification error messages
commit: 9b5a5a56c38ddf8fa5815294a1e0da999897e8b8
next prev parent reply other threads:[~2026-09-21 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 16:12 [PATCH proxmox, pve-{common,network,storage} v2 0/5] fix #7077: Improve error messages for ID verification Arthur Bied-Charreton
2026-02-06 16:12 ` [PATCH pve-common v2 1/1] fix #7077: Change JSON Schema attribute validation order Arthur Bied-Charreton
2026-09-21 12:35 ` Fiona Ebner
2026-09-21 13:58 ` superseded: " Arthur Bied-Charreton
2026-02-06 16:12 ` [PATCH pve-network v2 1/2] fix #7077: Enforce ID format in JSON schema definitions Arthur Bied-Charreton
2026-02-06 16:12 ` [PATCH pve-network v2 2/2] sdn: Remove unneeded registered formats Arthur Bied-Charreton
2026-02-06 16:12 ` [PATCH pve-storage v2 1/1] fix #7077: lvm: Improve ID verification error messages Arthur Bied-Charreton
2026-09-21 12:34 ` Fiona Ebner [this message]
2026-02-06 16:12 ` [PATCH proxmox v2 1/1] fix #7077: Improve SDN ID validation " Arthur Bied-Charreton
2026-03-31 20:39 ` partially-applied: [PATCH proxmox, pve-{common,network,storage} v2 0/5] fix #7077: Improve error messages for ID verification 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=178999406150.173954.11638196010192324859.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=a.bied-charreton@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.