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 989F81FF16F for ; Thu, 16 Jan 2025 17:31:03 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 38ED32E444; Thu, 16 Jan 2025 17:31:00 +0100 (CET) From: Aaron Lauterer To: pve-devel@lists.proxmox.com Date: Thu, 16 Jan 2025 17:30:55 +0100 Message-Id: <20250116163055.2619572-1-a.lauterer@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.034 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH manager] pvestatd: improve broadcast of node version-info X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Until now, the pvestatd did broadcast the pve-manager version only once after startup of the service. But there are some situations, where the local pmxcfs (pve-cluster) restarts and loses that information. Basically everytime we restart the pmxcfs without restarting pvestatd too. For example, on a cluster join, or if the pmxcfs has been restarted manually. By additionally checking if the local kv-store of the pmxcfs has any version info for the node, we can decide if another broadcast is necessary. Therefore after the next run of pvestatd, we should have the full version info available again. Signed-off-by: Aaron Lauterer --- This patch is preparation to get reliable version infos as I am picking of the patch series of Folke to include more metrics into the RRD data and summary graphs. [0] This was a big blocker and now with the major version change coming up, we at least can assume the latest 8.x installed as part of the update to PVE 9. Therefore, we should get this in with PVE 8. Additional patches for PVE 8 will follow to make the transition smoother. But as mentioned, this here is one of the things that needs to work reliably, which is why I submit the patch already now. [0] https://lore.proxmox.com/pve-devel/20231211144721.212071-1-f.gleumes@proxmox.com/ PVE/Service/pvestatd.pm | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm index 7fa003fe..03c578e1 100755 --- a/PVE/Service/pvestatd.pm +++ b/PVE/Service/pvestatd.pm @@ -527,7 +527,10 @@ sub update_sdn_status { my $broadcast_version_info_done = 0; my sub broadcast_version_info : prototype() { - if (!$broadcast_version_info_done) { + if ( + !$broadcast_version_info_done + || !keys PVE::Cluster::get_node_kv('version-info', $nodename)->%* + ) { PVE::Cluster::broadcast_node_kv( 'version-info', encode_json(PVE::pvecfg::version_info()), -- 2.39.5 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel