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 4E9E81FF14C for ; Fri, 29 May 2026 01:16:25 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 22E9E379D1; Fri, 29 May 2026 01:16:25 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Lukas Sichert Subject: applied: [PATCH manager v3] fix #4130: external metric: better handle failed connections Date: Fri, 29 May 2026 01:15:44 +0200 Message-ID: <178001014227.3746480.6855521598522405964.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260528112904.66865-1-l.sichert@proxmox.com> References: <20260528112904.66865-1-l.sichert@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: 1780010122458 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.005 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: TJSPA36ASD2KLWAX4SUVLYDXETYURSRU X-Message-ID-Hash: TJSPA36ASD2KLWAX4SUVLYDXETYURSRU 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, 28 May 2026 13:28:50 +0200, Lukas Sichert wrote: > When an external metric server configured to use TCP is unreachable, the > storage and VM indicators of the cluster nodes in the UI turn gray. This > is because, currently, a failed connection attempt raises an unhandled > exception, which aborts the status update flow. As the connection > attempts happen at the beginning of the update process, status > information is then not broadcasted within the system or across the > cluster. After five minutes without updates, the frontend marks the > indicators as gray. > > [...] Applied, thanks! [1/1] fix #4130: external metric: better handle failed connections commit: da5ba157af6f58337d116a02c004d6869687c3e1