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 757D01FF0B7 for ; Fri, 13 Nov 2026 04:08:53 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id EB21421922; Fri, 13 Nov 2026 04:04:39 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH v4 manager 24/36] pvestatd: apply the multipath configuration and report the node status Date: Fri, 13 Nov 2026 04:00:42 +0100 Message-ID: <20261113030146.1559030-25-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261113030146.1559030-1-t.lamprecht@proxmox.com> References: <20261113030146.1559030-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: 1794538915205 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.244 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: 4E4UBFQ5ATTETYSF6FETHXES7EAORPVG X-Message-ID-Hash: 4E4UBFQ5ATTETYSF6FETHXES7EAORPVG 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: The cluster-wide multipath configuration has to reach multipathd on every node, also after a reboot or a storage change, and the cluster needs to know which path state each node sees. Do both from the periodic status loop. Run this before the node, guest and storage updates. The storage status can block in LVM while all paths of a LUN are lost, which would delay the report of exactly that outage. Signed-off-by: Thomas Lamprecht --- PVE/Service/pvestatd.pm | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm index cec66e001..d9fbd2666 100755 --- a/PVE/Service/pvestatd.pm +++ b/PVE/Service/pvestatd.pm @@ -20,6 +20,7 @@ use PVE::RS::SDN::Fabrics; use PVE::NodeConfig; use PVE::Cluster qw(cfs_read_file); use PVE::Storage; +use PVE::Multipath::Status; use PVE::QemuServer; use PVE::QemuServer::Monitor; use PVE::LXC; @@ -814,6 +815,12 @@ sub update_status { my $status_cfg = PVE::Cluster::cfs_read_file('status.cfg'); + # apply the multipath configuration before the other updates: the storage status update can + # block in LVM while all paths of a LUN are lost + eval { PVE::Multipath::Status::update_node_status(); }; + $err = $@; + syslog('err', "multipath update error: $err") if $err; + eval { update_node_status($status_cfg, $pull_txn); }; $err = $@; syslog('err', "node status update error: $err") if $err;