From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id D43F81FF0A8 for ; Sat, 14 Nov 2026 22:33:22 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 4DD912163F; Sat, 14 Nov 2026 22:33:11 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Lucas Barros Subject: applied: [PATCH container] fix #8162: status: always return 'cpus' as number Date: Sat, 14 Nov 2026 22:33:01 +0100 Message-ID: <179469198023.2480055.7001419132572421409.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261107221120.13176-1-lucasbarros.kam@gmail.com> References: <20261107221120.13176-1-lucasbarros.kam@gmail.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: 1794691988204 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.232 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: AQOISL2RZILNWOVY3MA36A7JNH3WKEI2 X-Message-ID-Hash: AQOISL2RZILNWOVY3MA36A7JNH3WKEI2 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 List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Sat, 07 Nov 2026 19:11:20 -0300, Lucas Barros wrote: > For containers that only have 'cpulimit' set, the 'cpus' property of > the status API endpoints was encoded as a JSON string, for example > "cpus":"2", while the API schema declares it as a number. Clients that > decode the response strictly by the schema, like the Terraform > provider for Proxmox VE, fail to parse it. > > The config parser keeps values of 'number' typed options like > 'cpulimit' as string, while 'integer' options like 'cores' are > converted with int(). Explicitly convert the value to a number, so > 'cpus' has the same type regardless of which option it comes from. > > [...] Applied, thanks! [1/1] fix #8162: status: always return 'cpus' as number commit: a07edd2eda940504132f9300de6b730635e6a5ff