From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id CC3501FF13F
	for <inbox@lore.proxmox.com>; Thu, 26 Mar 2026 09:02:34 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 183947B98;
	Thu, 26 Mar 2026 09:02:55 +0100 (CET)
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Fiona Ebner <f.ebner@proxmox.com>
Subject: applied: [PATCH ha-manager] resources: fix type confusion regression
 for static stats
Date: Thu, 26 Mar 2026 09:02:01 +0100
Message-ID: <177451211780.846824.16354429218946808532.b4-ty@proxmox.com>
X-Mailer: git-send-email 2.47.3
In-Reply-To: <20260325150624.467936-1-f.ebner@proxmox.com>
References: <20260325150624.467936-1-f.ebner@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: 1774512088773
X-SPAM-LEVEL: Spam detection results:  0
	AWL                    -0.009 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: XYZYDFNSO6TJTMZN53KNRY6QAEZAKKPF
X-Message-ID-Hash: XYZYDFNSO6TJTMZN53KNRY6QAEZAKKPF
X-MailFrom: t.lamprecht@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 <pve-devel.lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Owner: <mailto:pve-devel-owner@lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Subscribe: <mailto:pve-devel-join@lists.proxmox.com>
List-Unsubscribe: <mailto:pve-devel-leave@lists.proxmox.com>

On Wed, 25 Mar 2026 16:06:18 +0100, Fiona Ebner wrote:
> Adding a container with an explicit number of 'cores' in the
> configuration would fail with an error like:
> 
> > unable to add service 'ct:105' usage to node 'pve9a2'
> > - error: invalid type: string "4", expected f64
> 
> Commit a299f1a ("move static service stats repository to
> PVE::HA::Usage::Static") accidentally broke this by removing the
> following hunk without adding new type coercions:
> 
> [...]

Applied, thanks!

[1/1] resources: fix type confusion regression for static stats
      commit: 8328cd271652eb55c42f09df092914ef93e8bcef