From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 6D7A91FF0DA for ; Thu, 19 Nov 2026 20:21:44 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id B3A23218D7; Thu, 19 Nov 2026 20:20:06 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH manager v5 30/41] ui: datacenter summary: show the cluster ID Date: Thu, 19 Nov 2026 20:19:02 +0100 Message-ID: <20261119191914.2336934-31-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261119191914.2336934-1-t.lamprecht@proxmox.com> References: <20261119191914.2336934-1-t.lamprecht@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795115960982 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.001 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) POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes 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 T_PDS_OTHER_BAD_TLD 0.01 Untrustworthy TLDs Message-ID-Hash: IQL7T5T2M3IYVRRX5PN64YMCWXZXL3XJ X-Message-ID-Hash: IQL7T5T2M3IYVRRX5PN64YMCWXZXL3XJ 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: Show the cluster ID below the cluster status in the health panel of the datacenter summary, so that administrators can look it up, for example to compare it with what a backup or inventory tool reports. That panel already polls /cluster/status, which has the ID on the cluster entry, or on the node entry of a node without a cluster, so this needs no further request. The cluster information in the cluster view would need one, and shows nothing for a node without a cluster. Signed-off-by: Thomas Lamprecht Reviewed-by: Dominik Csapak Tested-by: Dominik Csapak --- no changes since v4 changes v3 -> v4: * new in v4, suggested by Dominik www/manager6/dc/Health.js | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/www/manager6/dc/Health.js b/www/manager6/dc/Health.js index 773009bb..92277320 100644 --- a/www/manager6/dc/Health.js +++ b/www/manager6/dc/Health.js @@ -31,6 +31,7 @@ Ext.define('PVE.dc.Health', { let cluster = { iconCls: PVE.Utils.get_health_icon('good', true), text: gettext('Standalone node - no cluster defined'), + hintHtml: '', }; let nodes = { online: 0, @@ -48,6 +49,11 @@ Ext.define('PVE.dc.Health', { } numNodes = data.nodes; } + // a standalone node has the ID on its node entry, a cluster only on the cluster entry + if (data['cluster-id']) { + let clusterId = Ext.htmlEncode(data['cluster-id']); + cluster.hintHtml = `${gettext('Cluster ID')}: ${clusterId}`; + } } if (numNodes !== nodes.online + nodes.offline) { -- 2.47.3