Proxmox 8.x and Conntrack State Aware Migrations - Problem gives 400

[mikaelkrantz945]

2025-09-24 20:25:51,803 - ProxLB - CRITICAL - Balancing: Failed to migrate guest senode of type VM due to some Proxmox errors. Please check if resource is locked or similar.
2025-09-24 20:25:51,803 - ProxLB - DEBUG - Balancing: Failed to migrate guest senode of type VM due to some Proxmox errors: 400 Bad Request: Parameter verification failed. - {'with-conntrack-state': 'property is not defined in schema and the schema does not allow additional properties'}
2025-09-24 20:25:51,805 - ProxLB - DEBUG - Finished: exec_rebalancing_vm.
When trying to use default example config and just adding nodes and login info. Any idea why?

[damo2929]

What version of proxmox are you using as this feature was added in v9 and this code has been updated to support it

[mikaelkrantz945]

Using latest 8.x not yet went with production clusters to 9.x I dont believe it is yet production ready.
Is there any version of code I can use with 8.x?

[gyptazy]

conntrack aware migrations are a new feature of PVE 9, so it will not work with PVE 8.x. I'll adjust the code, so the current body will not contain all meta information in general, where the PVE API will stuck (see also: https://github.com/gyptazy/ProxLB/blob/main/proxlb/models/balancing.py#L164-L169). Afterwards, you'll be able to simple deactivate the contract state aware migrations in the config for PVE 8.

[gyptazy]

I just added the fix in PR #319 which will be part of the upcoming release 1.1.8.
On older PVE versions you then simply need to disable the conn track-aware migration by setting:

balancing:
  [...]
  with_conntrack_state: False

I'd be happy if you could test this. A related package including the fix can be found in the pipeline: https://github.com/gyptazy/ProxLB/actions/runs/17997388865

Cheers,
gyptazy

[gyptazy]

jftr, I've adjusted this to Q&A to provide an answer if someone falls into this issue in the meantime until the new version is released to find a fix. Also adjusted the topic to make it easier to find.

Thanks to @mikaelkrantz945 for testing this fix in #319!