The fix for this issue (linux upstream commit
306ed1728e8438caed30332e1ab46b28c25fe3d8 - netfilter: xtables: fix typo
causing some targets not to load on IPv6) has been applied to
noble/linux linux 6.8.0-58.60 as part of bug 2097575 (Noble update:
upstream stable patchset 2025-02-07) and released to noble-updates on
2025-04-16.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2104134
Title:
ovs/linuxbridge jobs running on ubuntu noble broken with latest kernel
6.8.0-56.58
Status in neutron:
Confirmed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Released
Bug description:
A commit[1] got backported to ubuntu noble kernel[2] which had an issue, Fix
is already available[3] in build[4] but not yet released. So all our
ovs/linuxbridge/fullstack/functional jobs running on ubuntu noble are impacted.
Master, 2025.1 or any releases running ovs jobs on noble are impacted.
Errors like below can be seen in these jobs
Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR
neutron.agent.l3.agent # Completed by iptables_manager
Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR
neutron.agent.l3.agent ; Stdout: ; Stderr: Warning: Extension MARK revision 0
not supported, missing kernel module?
Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR
neutron.agent.l3.agent ip6tables-restore v1.8.10 (nf_tables): unknown option
"--set-xmark"
Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR
neutron.agent.l3.agent Error occurred at line: 28
Mar 25 09:31:52.485392 np0040258543 neutron-l3-agent[62960]: ERROR
neutron.agent.l3.agent Try `ip6tables-restore -h' or 'ip6tables-restore --help'
for more information.
example failures:-
https://c00e7c7cf4b62bf664e8-ab9cdbb0aa9d61bf3167c27c9fa17003.ssl.cf1.rackcdn.com/openstack/fca5ab13dc674574953941a6e09eb935/testr_results.html
https://cf3ed66a65616b206bcc-d1906ed32ef7c4deba2ba4dd3d406176.ssl.cf1.rackcdn.com/openstack/071c7b51c1d448348e6e5dd4da8f4c9c/testr_results.html
https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_f60/openstack/f607cb89924e40019d37a617c6b009e8/testr_results.html
Until the new kernel with fix is released we need to remove the broken
noble images and pause new builds like it was done in past for same
issue in jammy
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091990/comments/3
[1]
https://github.com/torvalds/linux/commit/0bfcb7b71e735560077a42847f69597ec7dcc326
[2] https://bugs.launchpad.net/kernel-sru-workflow/+bug/2098244
[3]
https://github.com/torvalds/linux/commit/306ed1728e8438caed30332e1ab46b28c25fe3d8
[4] https://bugs.launchpad.net/kernel-sru-workflow/+bug/2102529
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2104134/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
