From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 5A9F21FF146 for ; Tue, 12 May 2026 12:05:16 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4FBB9D0C9; Tue, 12 May 2026 12:05:14 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Kefu Chai Subject: applied: [PATCH manager] api: cluster: ceph: fix osd metadata return schema Date: Tue, 12 May 2026 12:02:04 +0200 Message-ID: <177858011952.2029454.5634830327450701590.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260409114741.3119391-1-k.chai@proxmox.com> References: <20260409114741.3119391-1-k.chai@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: 1778580198792 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 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: NKPZ57JKOUPW24WD5DB5XJPGZGDV4DHU X-Message-ID-Hash: NKPZ57JKOUPW24WD5DB5XJPGZGDV4DHU 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 Thu, 09 Apr 2026 19:47:41 +0800, Kefu Chai wrote: > The 'osd' field used 'properties' inside a 'type: array', which is > invalid -- arrays use 'items' to describe their elements. The 'osd > metadata' command returns a bare JSON array where each element is an > object describing one OSD, so replace 'properties' with 'items'. > > The runtime behavior is unaffected; this is a schema-only correction. > > [...] Applied, thanks! [1/1] api: cluster: ceph: fix osd metadata return schema commit: 6639a26be73fc357952d43f19c246399112c96d5