From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 919FB1FF141 for ; Tue, 16 Jun 2026 15:15:56 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6F8599BBF; Tue, 16 Jun 2026 15:15:54 +0200 (CEST) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pve-devel@lists.proxmox.com, Jakob Klocker Subject: applied: [PATCH qemu-server] fix #7480: api: apply tag case-sensitivity setting on VM creation Date: Tue, 16 Jun 2026 15:12:43 +0200 Message-ID: <178161555167.2053720.7175473269512340397.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260522144218.38831-1-j.klocker@proxmox.com> References: <20260522144218.38831-1-j.klocker@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1781615664349 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.054 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: WA3D6MJFCKNSAZPY3HGQEXBMH7OYMWKV X-Message-ID-Hash: WA3D6MJFCKNSAZPY3HGQEXBMH7OYMWKV X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, 22 May 2026 16:42:18 +0200, Jakob Klocker wrote: > The case-sensitivity setting from datacenter.cfg was not checked > when tags were set during VM creation. Tags containing capital > letters were stored verbatim, while the same tags applied later > via the update endpoint were normalized. This led to inconsistent > behavior depending on whether a tag was set at creation or > afterwards. > > [...] Applied, thanks! I think a similar change would also be good when restoring VMs? [1/1] fix #7480: api: apply tag case-sensitivity setting on VM creation commit: 492347ae79844ef12e73fcbb164ebfb67a8b15be Best regards, -- Fabian Grünbichler