The openvswitch failures look like actual regressions, at least from a
quick look. E.g., from
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/amd64/o/openvswitch/20260115_172646_c4c8b@/log.gz, there is:
4193s ## ------------------------ ##
4193s ## Summary of the failures. ##
4193s ## ------------------------ ##
4193s Failed tests:
4193s openvswitch 3.3.4 test suite test groups:
4193s
4193s NUM: FILE-NAME:LINE TEST-GROUP-NAME
4193s KEYWORDS
4193s
4193s 74: system-traffic.at:2807 QoS - 64bit
4193s 75: system-traffic.at:2835 Ingress Policing - 64-bit
4193s
4193s ## ---------------------- ##
4193s ## Detailed failed tests. ##
4193s ## ---------------------- ##
4193s
4193s # -*- compilation -*-
4193s 74. system-traffic.at:2807: testing QoS - 64bit ...
4193s ../../tests/system-traffic.at:2810: modprobe openvswitch
4193s Module vport_lisp not loaded.
4193s Module vport_stt not loaded.
4193s ../../tests/system-traffic.at:2810: ovsdb-tool create conf.db
$abs_top_srcdir/vswitchd/vswitch.ovsschema
4193s ../../tests/system-traffic.at:2810: ovsdb-server --detach --no-chdir
--pidfile --log-file --remote=punix:$OVS_RUNDIR/db.sock
4193s stderr:
4193s 2026-01-15T17:06:39Z|00001|vlog|INFO|opened log file
/tmp/autopkgtest.dW64gj/build.M8T/src/_debian/tests/system-offloads-testsuite.dir/074/ovsdb-server.log
4193s ../../tests/system-traffic.at:2810: sed < stderr '
4193s /vlog|INFO|opened log file/d
4193s /ovsdb_server|INFO|ovsdb-server (Open vSwitch)/d'
4193s ../../tests/system-traffic.at:2810: ovs-vsctl --no-wait init -- set
Open_vSwitch . other_config:hw-offload=true
4193s ../../tests/system-traffic.at:2810: ovs-vswitchd --detach --no-chdir
--pidfile --log-file -vvconn -vofproto_dpif -vunixctl
4193s stderr:
4193s 2026-01-15T17:06:39Z|00001|vlog|INFO|opened log file
/tmp/autopkgtest.dW64gj/build.M8T/src/_debian/tests/system-offloads-testsuite.dir/074/ovs-vswitchd.log
4193s 2026-01-15T17:06:39Z|00002|ovs_numa|INFO|Discovered 4 CPU cores on NUMA
node 0
4193s 2026-01-15T17:06:39Z|00003|ovs_numa|INFO|Discovered 1 NUMA nodes and 4
CPU cores
4193s
2026-01-15T17:06:39Z|00004|reconnect|INFO|unix:/tmp/autopkgtest.dW64gj/build.M8T/src/_debian/tests/system-offloads-testsuite.dir/074/db.sock:
connecting...
4193s
2026-01-15T17:06:39Z|00005|reconnect|INFO|unix:/tmp/autopkgtest.dW64gj/build.M8T/src/_debian/tests/system-offloads-testsuite.dir/074/db.sock:
connected
4193s 2026-01-15T17:06:39Z|00006|netdev_offload|INFO|netdev: Flow API Enabled
4193s 2026-01-15T17:06:39Z|00007|tc|INFO|tc: Using policy 'none'
4193s ../../tests/system-traffic.at:2810: sed < stderr '
4193s /ovs_numa|INFO|Discovered /d
4193s /odp_execute_impl|INFO|Action implementation /d
4193s /vlog|INFO|opened log file/d
4193s /vswitchd|INFO|ovs-vswitchd (Open vSwitch)/d
4193s /reconnect|INFO|/d
4193s /dpif_netlink|INFO|Generic Netlink family .ovs_datapath. does not exist/d
4193s /ofproto|INFO|using datapath ID/d
4193s /netdev_linux|INFO|.*device has unknown hardware address family/d
4193s /ofproto|INFO|datapath ID changed to fedcba9876543210/d
4193s /dpdk|INFO|DPDK Disabled - Use other_config:dpdk-init to enable/d
4193s /netlink_socket|INFO|netlink: could not enable listening to all nsid/d
4193s /netdev_offload|INFO|netdev: Flow API Enabled/d
4193s /probe tc:/d
4193s /setting extended ack support failed/d
4193s /tc: Using policy/d'
[...]
That at least *sounds* like it could be caused by the iproute2 changes:
iproute2 (6.1.0-1ubuntu6.3) noble; urgency=medium
* Modify tc police to permit burst sizes up greater than 4GB (LP: #2125448)
- /d/p/2001-lib-Update-backend-of-print_size-to-accept-64-bit-si.patch
- /d/p/2002-tc-Add-get_size64-and-get_size64_and_cell.patch
- /d/p/2003-tc-Expand-tc_calc_xmittime-tc_calc_xmitsize-to-u64.patch
- /d/p/2004-tc-police-enable-use-of-64-bit-burst-parameter.patch
Jorge, please investigate these failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2125448
Title:
[SRU] Burst parameter of tc police only allows 4GB while the kernel
can support much more
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2125448/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
