Added multiple target nodes instead of a single node.

[PascalKu]

Imagine you have a cluster in which you migrate using High Availability Server. this is exactly the case I had. I have created a HA Group in Proxmox within which servers are automatically migrated in case of a failure or similar.

With this code change it doesn't matter now. You can specify an array of possible nodes where the QEMU can be located.

I also implemented my own change to your golang implementation (Telmate/proxmox-api-go#262) to manage this with HA Groups.

[aderumier]

Hi,

I'm currently working to fix it in the right ways proxmox side
(autofind nodename if /nodes/qemu/ is called)

https://lists.proxmox.com/pipermail/pve-devel/2023-May/057007.html

I'm trying to push for proxmox8

you can follow it here:

https://bugzilla.proxmox.com/show_bug.cgi?id=4689

[PascalKu]

It's been a long time since the last update in the feed. Anything happened in the past?

[lug-gh]

@PascalKu how to use this feature? It was merged, but documentation hasn't been updated.
Based on the source code Nodes: strings.Split(itemMap["nodes"].(string), ","), , I assume that I have to submit the hosts as a string, separated by a comma. target_node = "pve1,pve2,pve3"

However, I then get the error "Error: 400 Parameter verification failed." when applying.
It is displayed in the plan without any problems.
See #1081

[PascalKu]

Hi @lug-gh - do you still need help with this?

[lug-gh]

@PascalKu Yes, I still haven't figured it out.

[moonbaseDelta]

Hi, is this working only for VMs? Why not with LXC?

[PascalKu]

Hi, is this working only for VMs? Why not with LXC?

Because I only use QEMU - and nobody else updated it for LXC aswell.

[PascalKu]

@PascalKu Yes, I still haven't figured it out.

I'll now try to help you in your issue.