Can't connect to OVS with incus 7.5.1

Just updated the server, then I get this when attach a container to an ovs bridge:
incus profile add test ovs2

Error: Failed to start device "eth0": Failed to connect to OVS: Failed to connect to OVS: Failed to connect to OVS: failed to connect to unix:/run/openvswitch/db.sock: database Open_vSwitch validation error (3): Mapper Error. Object type ovsmodel.Datapath contains field CTZoneDefaultLimit (*int) ovs tag ct_zone_default_limit: Column does not exist in schema. Mapper Error. Object type ovsmodel.IPFIX contains field StatsInterval (*int) ovs tag stats_interval: Column does not exist in schema. Mapper Error. Object type ovsmodel.CTZone contains field Limit (*int) ovs tag limit: Column does not exist in schema

Old instances connect to the ovs bridge still working. Just can’t add new one. I think if I restart server, I won’t be able to connect to it again, so I won’t do it.

incus version

Client version: 7.5.1
Server version: 7.5.1

incus profile show ovs2

config: {}
description: connect to ovsbr2
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: ovsbr2
    type: nic
name: ovs2

The same container can connect to incus created network with native bridge driver.

And I can’t create network with openvswitch bridge driver.

incus network create mo bridge.driver=openvswitch

Error: Couldn't connect to OpenVSwitch: Failed to connect to OVS: Failed to connect to OVS: failed to connect to unix:/run/openvswitch/db.sock: database Open_vSwitch validation error (3): Mapper Error. Object type ovsmodel.IPFIX contains field StatsInterval (\*int) ovs tag stats_interval: Column does not exist in schema. Mapper Error. Object type ovsmodel.CTZone contains field Limit (\*int) ovs tag limit: Column does not exist in schema. Mapper Error. Object type ovsmodel.Datapath contains field CTZoneDefaultLimit (\*int) ovs tag ct_zone_default_limit: Column does not exist in schema

I just create a bridge use ovs-vsctl, and it worked.

I’m toasted. I downgrade incus and incus-base and incus-client, and it didn’t solve the problem. So it’s openvswitch-switch’s problem. I can’t find cache for it, so I can’t downgrade it. And my network depends on openvswitch-switch and incus, so my server can’t loose power till next openvswitch-switch show up.

Solved. Debian 12’s openvswitch version is 3.1.0, 13’s is 3.5.0. After upgrade to debian 13, everything seems work normal.

GitHub - zabbly/ovs: OVS builds · GitHub has backports