[Bug] Migration failed falsely

[tocfina]

Hey there! 👋 Thanks for taking the time to report this bug — we appreciate it!

Please keep in mind: PegaProx is developed and maintained entirely by volunteers in our free time. We do our best, but we can't work magic 🪄 — please be patient, we'll get to your issue as soon as we can.

Want to help keep PegaProx alive?

• ⭐ Star the project — it's free and helps a lot!
• 💖 Become a Sponsor — helps us dedicate more time to development
• 🤝 Contributing code or docs is always welcome too!

---

Describe the bug

In a three Node setup, HA enabled and affinity rules (with affinty negative) PegaProx says "⚠️ 1 VM(s) could not be migrated". This is container with affinty rule negative. The container is migrated (which i can see in Proxmox-UI).
I assume, due the HA and negative affinity rules, that the first attempt to migrate to a Node where the other container runs, fails, Proxmox then choose the next node.

Steps to Reproduce

1. Put Node in Migration state

Expected behavior

Pegaprox should wait for the correct state.

Environment

PegaProx Beta 0.9.7
VM
Debian 13
Firefox 149.0.2
No Proxy
Modern Layout

Logs

Apr 23 11:55:48 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:48,628] [PegaProx_HomeLab] INFO: [OK] Migration initiated for pihole to izar (Task: UPID:altair:002365E8:016B9619:69E9ECA4:hamigrate:105:root@pa>
Apr 23 11:55:48 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:48,812] [PegaProx_HomeLab] INFO: Node nihal: CPU 2.41%, RAM 19.40% (12.13 GB/62.53 GB), Score 21.81, Status: online
Apr 23 11:55:48 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:48,812] [PegaProx_HomeLab] INFO: Node izar: CPU 0.21%, RAM 21.58% (13.50 GB/62.53 GB), Score 21.79, Status: online
Apr 23 11:55:48 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:48,812] [PegaProx_HomeLab] INFO: Node altair: CPU 3.92%, RAM 25.98% (16.25 GB/62.53 GB), Score 29.91, Status: online [MAINTENANCE]
Apr 23 11:55:49 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:49,909] [PegaProx_HomeLab] INFO: Node altair: CPU 3.37%, RAM 25.98% (16.25 GB/62.53 GB), Score 29.35, Status: online [MAINTENANCE]
Apr 23 11:55:49 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:49,909] [PegaProx_HomeLab] INFO: Node izar: CPU 0.77%, RAM 21.55% (13.48 GB/62.53 GB), Score 22.33, Status: online
Apr 23 11:55:49 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:49,909] [PegaProx_HomeLab] INFO: Node nihal: CPU 0.92%, RAM 19.37% (12.11 GB/62.53 GB), Score 20.29, Status: online
Apr 23 11:55:50 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:50,655] [PegaProx_HomeLab] WARNING: Task UPID:altair:002365E8:016B9619:69E9ECA4:hamigrate:105:root@pam!pegaprox_098812: finished with exit statu>
Apr 23 11:55:50 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:50,656] [PegaProx_HomeLab] ERROR: [ERROR] Migration task failed for pihole
Apr 23 11:55:50 pegaprox-prod pegaprox[702]: [2026-04-23 11:55:50,656] [PegaProx_HomeLab] ERROR: [ERROR] Failed to evacuate pihole

## Screenshots
<!-- If applicable, add screenshots to help explain the problem. -->


## Checklist
- [ ] I have searched existing issues to make sure this is not a duplicate
- [ ] I am using the latest version of PegaProx