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 321E31FF146 for ; Tue, 09 Jun 2026 14:11:30 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 085C2EED0; Tue, 9 Jun 2026 14:11:30 +0200 (CEST) Message-ID: <23e92d00-f9b1-4493-b32e-b1985f5a5ec1@proxmox.com> Date: Tue, 9 Jun 2026 14:11:24 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH qemu-server] fix #7480: api: apply tag case-sensitivity setting on VM creation To: Jakob Klocker , pve-devel@lists.proxmox.com References: <20260522144218.38831-1-j.klocker@proxmox.com> Content-Language: en-US From: David Riley In-Reply-To: <20260522144218.38831-1-j.klocker@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1781007039533 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.204 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: FRP6LJ7PAKVGH5FAK6ZOB3TR4XOSV7VB X-Message-ID-Hash: FRP6LJ7PAKVGH5FAK6ZOB3TR4XOSV7VB X-MailFrom: d.riley@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: Thanks for sending in this patch.  I was able to reproduce the issue using the commands from the bugzilla report [0] for VMs. I was also unable to reproduce the issue for  LXCs as described in [0].  I used these commands to reproduce the error for VMs: qm create 130 --name tagtest --tags "cAsE-iNsEnSiTiVe" qm set 130 --tags "cAsE-iNsEnSiTiVe" And tested LXCs using this command: pct create 101 local:vztmpl/debian-13-standard_13.1-2_amd64.tar.zst \ --storage local-zfs --hostname test --nameserver 172.16.99.1 \ --tags "case-Sensitive" After applying the patch, case sensitivity works as expected on the  commandline as well as the WebUI.  I also tested this with the case-sensitive flag set ("Datacenter" -> "Options" -> "Tag Style Override"). Everything worked as expected. Tags were now case-sensitive on creation but also when setting them afterwards. Consider this as  Tested-by: David Riley [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7480 On 5/22/26 4:42 PM, Jakob Klocker wrote: > The case-sensitivity setting from datacenter.cfg was not checked > when tags were set during VM creation. Tags containing capital > > [...]