[Bug] UI reports that vms cant be assigned to pools

[hugobugomugo]

Describe the bug

assigning vms to pools reportedly fails, adds them enyway

Steps to Reproduce

1. settings -> Permissions -> pool permissions
2. hit blue settings button
3. create pool, try to assign any vm to said pool

Expected behavior

report back sucuessfully, remove already assigned vms from the selection

Environment

• PegaProx Version: 0.9.8
• Installation Method: docker
• OS: debian 13
• Browser: chromium 147.0.7727.117
• Behind Reverse Proxy? nginx
• UI? modern

Logs

first time adding:

Failed to add VM to pool

second time adding:

Proxmox API error: {"message":"update pools failed: VM 1003 is already a pool member\n","data":null}

Screenshots

Checklist

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

[hugobugomugo]

after exiting and entering the pool menu the already assigned vms are gone, but they should instead instantly vanish after assigning

[mkellermann97]

Hey @hugobugomugo, this is fixed — the "adds them anyway / reports failure" pattern was happening because PVE rejects pool re-assignment without an explicit allow-move=1 flag, and the "already a pool member" response from PVE was being surfaced as an error instead of being recognized as the post-condition we wanted. Patched in 0.9.8.2 (released a couple of weeks ago, then carried into 0.9.9): the API call now passes allow-move=1 for repool, and the "already a pool member" branch returns success/idempotent rather than error.

Easiest path: docker pull the latest tag (or upgrade via Settings → Updates inside the app). Should be smooth from there.

Closing as fixed — reopen with logs from /var/log/pegaprox/ or the docker container if it still misbehaves on 0.9.9. PegaProx is donation-funded, https://opencollective.com/pegaprox if it ever spares you a debugging afternoon.

— MK