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 9310B1FF09C for ; Mon, 05 Oct 2026 17:57:52 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id C047B2167B; Mon, 05 Oct 2026 17:57:48 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 05 Oct 2026 17:57:43 +0200 Message-Id: To: =?utf-8?q?Michael_K=C3=B6ppl?= , Subject: Re: [PATCH cluster/docs/manager/widget-toolkit v4 0/8] add warning messages for high token timeouts in clusters From: =?utf-8?q?Michael_K=C3=B6ppl?= X-Mailer: aerc 0.22.0 References: <20260605153819.310048-1-m.koeppl@proxmox.com> In-Reply-To: <20260605153819.310048-1-m.koeppl@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1791215863146 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.314 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: 2HEOROCFVDOLLXORKHHQTS4VRYVIFMOR X-Message-ID-Hash: 2HEOROCFVDOLLXORKHHQTS4VRYVIFMOR X-MailFrom: m.koeppl@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: Ping, still applies Also checked with Friedrich if this is still relevant. The changes would still make sense to add since changing the token coefficient is possible and in certain scenarios a sensible approach, which the docs also state. I also tested through all the functionality again, just to be sure. On Fri Jun 5, 2026 at 5:38 PM CEST, Michael K=C3=B6ppl wrote: > This patch series introduces warnings informing users about high token > timeouts in their clusters. A recent change [0] lowered the token > coefficient for clusters and allowed adapting it. However, this change > only affects new clusters. As described in [1], users with existing > cluster should be informed about the high token timeouts in their > configurations and what they can do to alleviate this problem. > > Thus, warnings are added to the `pvecm status` command as well as to the > cluster join info dialog in the web UI. The warning in the web UI warns [snip]