public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Daniel Kral <d.kral@proxmox.com>,
	Gabriel Goller <g.goller@proxmox.com>
Cc: pve-devel <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [RFC PATCH manager] migrate: fix conntrack migration and ha-resources checkbox
Date: Fri, 1 Aug 2025 09:35:25 +0200	[thread overview]
Message-ID: <cc9e1378-7f05-4942-9e9b-0eaf9797ffcd@proxmox.com> (raw)
In-Reply-To: <DBQWK7GWARLN.36D8IBMU6RHRW@proxmox.com>

Am 01.08.25 um 09:11 schrieb Daniel Kral:
> Thanks for spotting that!
> 
> On Fri Aug 1, 2025 at 8:38 AM CEST, Thomas Lamprecht wrote:
>> Am 31.07.25 um 17:58 schrieb Gabriel Goller:
>>> +                console.warn(`failed to query /capabilites/qemu/migration on '${target}':`);
>>> +                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') {
>>
>> If it exists this is always an array per the schema though,
>> so the following might be enough:
>>
>> if (typeof comigratedHAResources === 'array') {
>>
>> Or use the ExtJS frameworks' Ext.isIterable() while under the hood it's a bit more
>> heuristic than your check, it should cover all (for us) relevant cases
>>
>> if (Ext.isIterable(comigratedHAResources)) {
>>
>> Your variant might be fine as Proxmox.Utils method though, but rather overkill for
>> now.
> 
> Another even simpler version that we use in the function already (e.g.
> right above for blockingHAResources) is to just fallback to an empty
> array, i.e.
> 
> let comigratedHAResources = migrateStats['comigrated-ha-resources'] ?? [];
> if (comigratedHAResources.length) {
> ...

FWIW, the backend is wrongly setting this to an object by default, that
might contribute to the error here, or even be its actual source!

I'm fixing this up there and will also do a s/comigrated/dependent/ as
that's what this actually describes, that these resources then normally
also migrate is the result not the cause, and might change with node
affinity rules being mixed with non-strict resource once in the future.

> 
> 
> Either way, the fix should also be done for checkLxcPreconditions(...),
> because there it's missing the check too.
> 
Will also take another look at the backend here.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-08-01  7:34 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 [this message]
2025-08-01  8:02       ` Daniel Kral
2025-08-01 15:44 ` Thomas Lamprecht

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=cc9e1378-7f05-4942-9e9b-0eaf9797ffcd@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.kral@proxmox.com \
    --cc=g.goller@proxmox.com \
    --cc=pve-devel-bounces@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal