From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Gabriel Goller <g.goller@proxmox.com>
Subject: Re: [pve-devel] [RFC PATCH manager] migrate: fix conntrack migration and ha-resources checkbox
Date: Fri, 1 Aug 2025 17:44:08 +0200 [thread overview]
Message-ID: <fb8f1cb9-5b6f-4dee-ae2c-dace2fc63ce6@proxmox.com> (raw)
In-Reply-To: <20250731155846.277381-1-g.goller@proxmox.com>
Am 31.07.25 um 17:58 schrieb Gabriel Goller:
> The checkbox wasn't displayed and following errors were on the console:
>
> failed to query /capabilites/qemu/migration on '': [object Object] pvemanagerlib.js:20401:25
> Uncaught (in promise) TypeError: comigratedHAResources is not iterable
> checkQemuPreconditions https://172.16.0.18:8006/pve2/js/pvemanagerlib.js?ver=9.0.0~17:20595
>
> Error is an object, so we need to print it in the next line, otherwise
> only [object Object] is shown. Check if comigratedHAResources is
> iterable, otherwise don't iterate over it.
>
> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> ---
>
> Tested this quickly but no idea if it's correct. Maybe Daniel and
> Christoph could have a look at it.
>
> www/manager6/window/Migrate.js | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/www/manager6/window/Migrate.js b/www/manager6/window/Migrate.js
> index b5ecb9603cf1..c884fbddd1aa 100644
> --- a/www/manager6/window/Migrate.js
> +++ b/www/manager6/window/Migrate.js
> @@ -254,7 +254,8 @@ Ext.define('PVE.window.Migrate', {
> } catch (err) {
> // Only emit a warning in the case the target node does not (yet) support the
> // `capabilites/qemu/migration` endpoint and simply treat all features as unsupported.
> - console.warn(`failed to query /capabilites/qemu/migration on '${target}': ${err}`);
> + console.warn(`failed to query /capabilites/qemu/migration on '${target}':`);
this I pushed a separate patch for:
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=8cc5475193930f994db38b77b518edc74f3aac90
> + console.warn(err);
> }
>
> me.fetchingNodeMigrateInfo = false;
> @@ -447,7 +448,7 @@ Ext.define('PVE.window.Migrate', {
> }
>
> let comigratedHAResources = migrateStats['comigrated-ha-resources'];
> - if (comigratedHAResources !== undefined) {
> + if (comigratedHAResources !== undefined && typeof comigratedHAResources[Symbol.iterator] === 'function') {
This became obsolete when fixing the backend:
https://git.proxmox.com/?p=pve-container.git;a=commitdiff;h=0b6b4bde49244711a0ba31b09e9ccf23ec03f03b
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=eba40484c906ad8bd2d0928f2a7f36b79a53b145
And FWIW, I then made another follow-up change to not even return that property
if the CT/VM is not HA managed, and changed the name from 'comigrated-ha-resources'
to 'dependent-ha-resources' for both pve-container and qemu-server + the
maching pve-manager UI patch.
Thanks in any case for this here, as talked offlist, it might still be nice to have a generic
helper in widget-toolkit, otoh. the backend type-confusion bug would not be caught by
testing with that in the first place ^^ (but also not have happened in rust ;)
> for (const sid of comigratedHAResources) {
> const text = Ext.String.format(
> gettext(
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-08-01 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 15:58 Gabriel Goller
2025-08-01 6:38 ` Thomas Lamprecht
2025-08-01 7:11 ` Daniel Kral
2025-08-01 7:35 ` Thomas Lamprecht
2025-08-01 8:02 ` Daniel Kral
2025-08-01 15:44 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb8f1cb9-5b6f-4dee-ae2c-dace2fc63ce6@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.