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 D804D1FF133 for ; Mon, 11 May 2026 11:47:30 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 16ED81057D; Mon, 11 May 2026 11:47:26 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH manager v3 17/17] ui: migrate: display precondition messages for ha node affinity Date: Mon, 11 May 2026 11:46:38 +0200 Message-ID: <20260511094707.142930-18-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260511094707.142930-1-d.kral@proxmox.com> References: <20260511094707.142930-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1778492723925 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.077 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: 646ZFMMB6K4SKM7DJPO7X2YFMBHAVMKT X-Message-ID-Hash: 646ZFMMB6K4SKM7DJPO7X2YFMBHAVMKT X-MailFrom: d.kral@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: Extend the VM and container precondition check to show whether a migration of the VM/container cannot be completed because of a node affinity rule restricting the HA resource from being migrated to a specific node. The migration is blocked by the HA Manager's CLI and state machine anyway, so this is more of an informational heads-up. Signed-off-by: Daniel Kral Reviewed-by: Fiona Ebner --- changes v2 -> v3: - none www/manager6/window/Migrate.js | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/www/manager6/window/Migrate.js b/www/manager6/window/Migrate.js index ff80c70c..8cac54ea 100644 --- a/www/manager6/window/Migrate.js +++ b/www/manager6/window/Migrate.js @@ -432,6 +432,11 @@ Ext.define('PVE.window.Migrate', { ), sid, ); + } else if (cause === 'node-affinity') { + reasonText = Ext.String.format( + gettext('HA resource {0} is not allowed on the selected target node'), + sid, + ); } else { reasonText = Ext.String.format( gettext('blocking HA resource {0} on selected target node'), @@ -522,6 +527,11 @@ Ext.define('PVE.window.Migrate', { ), sid, ); + } else if (cause === 'node-affinity') { + reasonText = Ext.String.format( + gettext('HA resource {0} is not allowed on the selected target node'), + sid, + ); } else { reasonText = Ext.String.format( gettext('blocking HA resource {0} on selected target node'), -- 2.47.3