This bug is awaiting verification that the linux/5.15.0-132.143 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still exists, change the tag 'verification-needed-jammy-
linux' to 'verification-failed-jammy-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux

-- 
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/2089699

Title:
  kernel:nft "Could not process rule: Device or resource busy" on
  unreferenced chain

Status in linux package in Ubuntu:
  New
Status in linux-gke package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux-gke source package in Jammy:
  In Progress

Bug description:
  We see some nftables/netfilter problems after kernel upgrade from 
5.15.0-1061-gke to 5.15.0-1067-gke.
  Correct transaction with nft fails with "Error: Could not process rule: 
Device or resource busy"
  which usually means a deleted chain is referenced, but you can see it's not.
  Full nft table dump + transaction + error is in the attached file.
  This is logs from kubernetes CI, which started failing immediately after 
mentioned kernel update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089699/+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

Reply via email to