Thanks @dannf for updating the bug! The SRU description looks good to me
and everything seems reasonable, same with the plan.
I'll keep monitoring this tracker and we'll proceed once oracular will
be open.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hello, any progress on this? Now that ubuntu-fan is officially
deprecated in Noble can we simply sync iproute2 with Debian? Is there
any pending activity / requirement that are preventing this? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
[Impact]
In order to provide ubuntu-fan we need to maintain additional kernel
SAUCE patches that are currently conflicting with upstream code,
potentially breaking networking eBPF APIs.
To prevent such incompatibility the whole patch set requires a major
redesign.
However,
According to the information that I collected (asking around,
investigating, etc.), it seems that there are no critical users of
ubuntu-fan.
Moreover, considering the impact of the ubuntu-fan kernel patches (that
would require a major refactoring to avoid breaking the network eBPF
ABI), we
Public bug reported:
tests-in-lxd seems to fail to download the lxd image used for the test (or
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)
Instance published with fingerprint:
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
It could be related to #1991691 if you're using the kernel currently in
release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1992979
Title:
kinetic ppc64le reporting
All the initramfs-tools autopkgtest tests seem to run fine on a recent
kernel (5.19) with the debdiff in attach applied.
** Patch added: "initramfs-tools-increase-ram-2GB.debdiff"
Public bug reported:
[Impact]
Some autopkgtest tests are failing due to out-of-memory conditions,
especially amd64-ata-only and net.
It seems that we are creating a VM with 1GB only to run the amd64-ata-
only test and even just 512MB for the net test.
It probably makes sense to create larger
** Also affects: network-manager (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: urfkill (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this
This seems to fix the test failure.
** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592621/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff
** Patch removed:
** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
[Impact]
test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:
e70344c05995 ("block: fix default IO priority handling")
Previously setting IOPRIO_CLASS_NONE for a process would report
** Description changed:
The wpa-dhclient autopkgtest is always failing without wireless-tools
- installed. Maybe wireless-tools should be an explicit dependency of
- network-manager.
+ installed. Maybe wireless-tools should be added to the test dependencies
+ (debian/tests/control).
--
You
Public bug reported:
The wpa-dhclient autopkgtest is always failing without wireless-tools
installed. Maybe wireless-tools should be an explicit dependency of
network-manager.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
updated debdiff in attach FWIW
** Patch added: "apparmor-fix-autotests.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5562493/+files/apparmor-fix-autotests.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@alexmurray thanks for the update! BTW I found another issue with test-
network.py: this test is failing because utils/apparmor/rule/network.py
is missing the mctp protocol (in network_domain_keywords[]).
I checked upstream, but I couldn't find any fix for this, do you want me
to open another
Simple fix in the attached debdiff
** Patch added: "apparmor-fix-test-aa-notify.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5561612/+files/apparmor-fix-test-aa-notify.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
+ [Impact]
+
+ test-aa-notify is also checking if the output of `aa-notify --help`
+ matches a specific text. However it looks like this output has changed
+ in jammy so the autopkgtest is reporting errors like this:
+
05:17:31 ERROR| [stderr] === test-aa-notify.py ===
Public bug reported:
05:17:31 ERROR| [stderr] === test-aa-notify.py ===
05:17:31 ERROR| [stderr] .ssF.
05:17:31 ERROR| [stderr]
==
05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
05:17:31 ERROR|
Adding also focal, because with the new linux-hwe-5.15 we get the same
failure.
** Summary changed:
- update iproute2 in jammy
+ update iproute2
** Also affects: iproute2 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member
debdiff in attach can help to prevent this problem from happening
(bumping up image file to 2GB).
** Patch added:
"initramfs-tools-prevent-out-of-disk-space-error-during-autotest.debdiff"
Public bug reported:
In debian/tests/prep-image we create an image file of 1GB, but recent
jammy cloud images are (barely) bigger than that, for example the
current one uncompressed is 1001MB...
Maybe we should consider to create image files of 2GB or even bigger,
considering that we are only
This failure isn't happening anymore, we can close this one.
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
New iproute has been merged in jammy. We can close this.
** Changed in: iproute2 (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
New iproute has been merged in jammy. We can close this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1951390
Title:
update iproute2 in jammy
Status in iproute2
Public bug reported:
I'm getting the following errors when running systemd autopkgtest on the
latest Jammy 5.15 Ubuntu kernel:
Received SIGCHLD from PID 2674 (sh).
Child 2674 (sh) died (code=killed, status=13/PIPE)
exec-ignoresigpipe-no.service: Failed to read oom_kill field of memory.events
debdiff against Debian iproute2 5.15.0-1 (re-applied Ubuntu Fan driver).
v2: added this tracking bug to the changelog entry.
** Patch added: "iproute2-update-to-5.15-v2.debdiff"
** Patch added: "iproute2-update-to-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541716/+files/iproute2-update-to-5.15.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: iproute2 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1951390
Title:
update iproute2 in
Public bug reported:
Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
In-situ OAM (IOAM6). This lack of support is also triggering the
following kernel selftest failure:
# selftests: net: ioam6.sh
# SKIP: iproute2 too old, missing ioam command
not ok 1 selftests: net:
New debdiff with the enabled autopkgtest test case. (I'm assuming the
Suggests: packages are installed when we run autopkgtest, so I'm not
doing anything special to install nftables).
** Patch added: "iptables-nft-fix-counters-v2.debdiff"
Alright I figured out why the tests were failing, simply nftables wasn't
installed in my test environment. I see that nftables is reported in the
Suggests: list.
@xnox IIRC we are installing all the suggests when we run the autotest,
is it correct?
--
You received this bug notification because
@xnox interestingly enough 2 tests are failing with nft and 1 test in
legacy running `./run-tests.sh --host`:
W: [FAILED] ././testcases/ipt-restore/0004-restore-race_0: expected 0 but
got 1
...
I: legacy results: [OK] 49 [FAILED] 1 [TOTAL] 50
W: [FAILED]
** Description changed:
+ [Impact]
+
Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
is always failing. Initially I thought it was a kernel issue, but
debugging further I found that the reason is that with Impish we're
using iptables-nft by default instead of
** Changed in: iptables (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: iptables (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
The debdiff in attach seems to solve the problem.
Without this fix applied:
$ sudo ./tools/testing/selftests/net/xfrm_policy.sh
PASS: policy before exception matches
FAIL: expected ping to .254 to fail (exceptions)
...
With this fix applied:
$ sudo ./tools/testing/selftests/net/xfrm_policy.sh
FYI, I've tested the latest iptables from
https://git.netfilter.org/iptables/ and the test passes also with
iptables-nft.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
Public bug reported:
Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
is always failing. Initially I thought it was a kernel issue, but
debugging further I found that the reason is that with Impish we're
using iptables-nft by default instead of iptables-legacy.
This test
Makes sense, thanks for looking at this Christian!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1943441
Title:
lxc: lxc-test-parse-config-file failure
Status in lxc
Public bug reported:
I'm getting the following error with the lxc kernel autotest on impish:
08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load:
expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for
config key "lxc.selinux.context" do not match
Public bug reported:
It looks like the option "lxc.rootfs.options = ro" is not honored with
lxc 4.0.10-0ubuntu3 and it used to work with lxc 4.0.6-0ubuntu1 (kernel
is the same, I'm testing this with 5.13.0-13.13).
Output of the test:
09:12 ubuntu@impish$ sudo ./src/tests/lxc-test-rootfs
+
Public bug reported:
The lxc autotest is failing with the following error(s) on the latest
kernel linux-unstable 5.13:
FAIL: lxc-tests: lxc-test-apparmor (1s)
---
failed - opened /sys/kernel/uevent_helper
---
PASS: lxc-tests: lxc-test-apparmor-generated (0s)
PASS: lxc-tests:
New debdiff that contains a proper reference to the upstream patch.
Thanks!
** Patch added: "apparmor-utils-support-cap-checkpoint-restore.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1923432/+attachment/5486963/+files/apparmor-utils-support-cap-checkpoint-restore.debdiff
@sbeattie sorry I didn't notice your comment, I can post another debdiff
that includes the proper upstream commit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1923432
** Patch added: "apparmor-utils-support-cap-checkpoint-restore.debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1923432/+attachment/5486955/+files/apparmor-utils-support-cap-checkpoint-restore.debdiff
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
It looks like /etc/apparmor/severity.db is missing the new capability
CAP_CHECKPOINT_RESTORE.
This causes the following regression test failure:
ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1
This
Public bug reported:
After enabling the -proposed ppa in Hirsute (21.04) I'm getting the
following error:
ubuntu@hirsute:~$ sudo su -
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
ubuntu@hirsute:~$ ls -l /usr/bin/sudo
-rwsr-xr-x 1 2001 2501 190952 Feb 10 11:42
** Attachment added: "perf object files / build tree"
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1887397/+attachment/5392329/+files/perf-build-fail.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Adding the specific command that is reporting error:
gcc -Wbad-function-cast -Wdeclaration-after-statement -Wformat-security
-Wformat-y2k -Winit-self -Wmissing-declarations -Wmissing-prototypes
-Wnested-externs -Wno-system-headers -Wold-style-definition -Wpacked
-Wredundant-decls
Public bug reported:
After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
is failing with the following error:
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@'
50 matches
Mail list logo
