From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 0853D1FF13B for ; Mon, 08 Jun 2026 13:56:08 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D555A1B274; Mon, 8 Jun 2026 13:56:07 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 08 Jun 2026 13:55:33 +0200 Message-Id: From: "Lukas Sichert" 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 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: 1780919690119 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.286 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: S7B5VLBU6TL53TWUF6F3TPY64IGP3QL2 X-Message-ID-Hash: S7B5VLBU6TL53TWUF6F3TPY64IGP3QL2 X-MailFrom: l.sichert@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 2026-06-05 17:38, 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. Tested this using a three node cluster by just manually increasing the token timeout. The messages in the UI and cli get displayed correctly. Also the links to the documentation work. Feel free to use my Tested-by in future version if only smaller UI things are changed. Tested-by: Lukas Sichert