[Bug] Visual Element: Cross Cluster Migration shows nothing in the CPU/Mem % text

[KowMangler]

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

When doing a cross cluster migration one of the steps doesn't display cpu/mem of the target cluster

Steps to Reproduce

1. Select a VM
2. Start a Cross Cluster Migration
3. Select a cluster to migrate to

Expected behavior

I am not sure what the intent is but my assumption is that the migration page should show the used or available CPU/Mem on the target cluster.

Environment

• PegaProx Version: PegaProx Beta 0.9.10
• Installation Method: script
• OS: Debian 13
• Browser: Google Chrome 148.0.7778.167
• Behind Reverse Proxy? NO
• UI? Corporate

Logs

Screenshots

I can confirm the cluster does have usage as does that node:

Checklist

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

[mkellermann97]

Hey @KowMangler — picked this one up just now.

Confirmed the bug: at vm_modals.js:3256 the dropdown reads n.cpu_percent and n.mem_percent off each target-node record, but /api/clusters/<id>/nodes was returning the raw PVE response unchanged — and PVE only gives cpu (a 0..1 fraction), mem, maxmem. So n.cpu_percent?.toFixed(1)% short-circuited to nothing → blank text. Same for RAM.

Backend-only fix landed on Testing (commit 5d1ae80). get_cluster_nodes() now enriches each record with cpu_percent = cpu * 100 and mem_percent = mem / maxmem * 100 before jsonify. Offline nodes that don't have those raw fields get skipped (so they stay empty, but no exception). The cached fallback also picks the enriched values up.

Verified live against the dev cluster — got real values like pve1 cpu_percent=6.38 mem_percent=38.21 and dedicated-zap106363-2 cpu_percent=28.14 mem_percent=32.08. So the dropdown should now show actual percentages once this rolls into a release.

Donations at https://opencollective.com/pegaprox if the bug-report-to-fix loop on this kind of paper-cut keeps earning its keep — appreciated.

— Marcus

[mkellermann97]

Hey @KowMangler — v0.9.10.3 shipped: https://github.com/PegaProx/project-pegaprox/releases/tag/v0.9.10.3

The cpu_percent / mem_percent enrichment is in. After upgrading, the cross-cluster migration target-node dropdown will show real percentages (e.g. pve1 (online) - CPU: 6.4% RAM: 38.2%) instead of the empty CPU: % RAM: % you reported. Backend now computes them from the raw PVE cpu (0..1 fraction) and mem/maxmem fields and ships them as additive properties on /api/clusters/<id>/nodes — no other consumer is affected.

Closing as completed. If percentages still look off after the upgrade (e.g. capped at 100 when they shouldn't be, or wrong for specific node types), drop a fresh ticket and we'll take that separately.

Donations at https://opencollective.com/pegaprox if these dashboard polish fixes earn their keep.

— Marcus