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 503881FF13C for ; Thu, 16 Apr 2026 07:58:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B53AB216A2; Thu, 16 Apr 2026 07:58:37 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Thu, 16 Apr 2026 07:58:01 +0200 Message-Id: Subject: Re: [PATCH manager v2] ui: ha: add disarm/re-arm button From: "Dominik Rusovac" To: "Dominik Csapak" , X-Mailer: aerc 0.20.0 References: <20260415064118.33290-1-d.rusovac@proxmox.com> <900084a5-9466-4a98-b653-2c97fc863f38@proxmox.com> In-Reply-To: X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776319003462 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.471 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 Message-ID-Hash: FOI4CVYI6XNNV6IWNNKBSFHUZKU645SA X-Message-ID-Hash: FOI4CVYI6XNNV6IWNNKBSFHUZKU645SA X-MailFrom: d.rusovac@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 Wed Apr 15, 2026 at 4:18 PM CEST, Dominik Csapak wrote: > > > On 4/15/26 3:30 PM, Dominik Rusovac wrote: >> thx for the comments! I will send a v3 >>=20 >> On Wed Apr 15, 2026 at 2:32 PM CEST, Dominik Csapak wrote: >>> what i miss with using these is some feedback when i activated them. >>> >>> This is probably more due to the backend decision, but >>> when clicking arm/disarm, there is nothing happening in the gui at >>> first, no spinning icon, no change in state.. >>=20 >> regarding feedback after activating either of them: one can see the >> Status changing in the Status panel, which exactly traces what's going >> on for every node, in particular it reveals the armed-state in the >> Status of fencing >>=20 >> if that's not enough feedback, I'd look into other possible solutions in >> more detail > > on my test machine, it multiple seconds from clicking ok to > the status actually changing, so this might be confusing, especially > if the cluster/connection is not the fastest and the updates > take longer to arrive. > ok, I see your point. I will try to come up with a solution >>=20 >>> >>> I think there are a few possible solutions on this, but >>> i'm not super deep in the ha stack, so sorry in advance if >>> some can't work: >>> * use a worker that waits for the change of the ha state, e.g. >>> via polling. this could directly be shown in the gui >>> * mark the requested state immediately somewhere and return >>> it with the overall ha state, so we see in the gui what is happeni= ng >>> * 'fake' the progress until we see a status change >>> (i don't really like this, since it's prone to errors when e.g. >>> one admin disarms, the other arms again, but the gui does not >>> get an updated state in the meantime) >>> [snip]