systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
systemd (Ubuntu) | Status tracked in Hirsute | |||||
| Bionic |
Medium
|
Dan Streetman | |||
| Focal |
Medium
|
Dan Streetman | |||
| Groovy |
Medium
|
Dan Streetman | |||
| Hirsute |
Medium
|
Dan Streetman |
Bug Description
[impact]
autopkgtest failure when running with 5.8 kernel, if systemd is built with earlier kernel (e.g. 5.4)
[test case]
see autopkgtest results, e.g. links in original description below
[regression potential]
as this only fixes a test case, any regression would likely result in an incorrectly passing, or incorrectly failing, test.
[scope]
this is needed for b/f/g/h.
this bug was introduced by upstream commit 23cc81e7c22 which first added testing for 'invalid' cap numbers, but incorrectly using capability_
this is fixed upstream by commit ebc815cd1c647fa
Also note that even though the 5.8 kernel is not planned to be released for Bionic, this test also runs at build time, and since the LP build farm builds inside chroots, if the build farm ever moved up to Focal with a 5.8 kernel, the build of systemd for Bionic would start failing (since it would still be building using the older kernel headers, inside the chroot), so this does need to be fixed in Bionic systemd as well.
[other info]
there is a non-test bug related to this in bug 1905245
[original description]
Testing failed on:
amd64: https:/
arm64: https:/
ppc64el: https:/
s390x: https:/
The failing testcases are:
- root-unittests
Assertion 'capability_
ion test_capability
FAIL: test-cap-list (code: 134)
- upstream
TEST-24-UNIT-TESTS:
--- test-cap-list begin ---
Assertion 'capability_
ion test_capability
--- test-cap-list end ---
Both seem to be failing with the same assertion.
These tests are successful on Focal with linux 5.4, therefore they would regress when upgrading the kernel from 5.4 to 5.8.
tags: | added: kernel-adt-failure |
summary: |
systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8 - 5.8.0-30.32~20.04.1 |
Changed in systemd (Ubuntu Focal): | |
status: | New → Confirmed |
Changed in systemd (Ubuntu): | |
status: | New → Invalid |
description: | updated |
Dan Streetman (ddstreet) wrote : | #1 |
@ddstreet thanks for pointing to that other bug report.
After applying the fix from https:/
$ ./systemctl show -p CapabilityBound
CapabilityBound
But the testcase fails a little bit down the line:
$ ./test-cap-list
cap_chown = 0
cap_dac_override = 1
cap_dac_read_search = 2
[...]
cap_block_suspend vs. cap_block_suspend
cap_audit_read vs. cap_audit_read
Assertion 'streq(t1, t)' failed at src/test/
Aborted (core dumped)
So I'm wondering if some other fixes are needed as well do fix the testcase.
Dan Streetman (ddstreet) wrote : | #4 |
yeah, the testcase will need to be fixed with something like
https:/
description: | updated |
Changed in systemd (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Focal): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Hirsute): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Groovy): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Focal): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Bionic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in systemd (Ubuntu Groovy): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Hirsute): | |
importance: | Undecided → Medium |
Changed in systemd (Ubuntu Groovy): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Focal): | |
status: | Confirmed → In Progress |
Changed in systemd (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in systemd (Ubuntu Hirsute): | |
status: | Invalid → In Progress |
Dan Streetman (ddstreet) wrote : | #5 |
@rbalint, fyi since this is a testcase-only fix, I just pushed to the hirsute repo, assuming you wouldn't mind.
https:/
description: | updated |
description: | updated |
description: | updated |
Changed in systemd (Ubuntu Hirsute): | |
status: | In Progress → Fix Committed |
Launchpad Janitor (janitor) wrote : | #6 |
This bug was fixed in the package systemd - 247.1-4ubuntu1
---------------
systemd (247.1-4ubuntu1) hirsute; urgency=medium
[ Dan Streetman ]
* d/p/lp1905044-
Fix test use of new cap numbers with 5.8 kernel (LP: #1905044)
https:/
[ Balint Reczey ]
* Merge to Ubuntu from Debian unstable
* Refresh patches
- Dropped changes:
* debian/
(Upstream code has been changed in a similar way)
* debian/
* debian/
* d/p/lp1905044-
(Present in upstream 247.)
* debian/udev.NEWS: Mention udev rules changes in 247
File: debian/udev.NEWS
https:/
* Don't start systemd-
It fails and is not likely to be useful.
File: debian/
https:/
* test: use modern qemu numa arguments (LP: #1908259)
File: debian/
https:/
systemd (247.1-4) unstable; urgency=medium
[ наб ]
* debian/
an explicit path was passed (Closes: #970213)
* debian/
messages and uninstallation to 90-loaderentry.
[ Michael Biebl ]
* sd-device: keep escaped strings in DEVLINK= property (Closes: #976699)
systemd (247.1-3) unstable; urgency=medium
* d/t/timedated: Ignore return code of dbus-monitor in wait_mon()
We are not really interested in the return code and error messages from
dbus-monitor after killing it, so ignore them to avoid undesired
autopkgtest failures.
systemd (247.1-2) unstable; urgency=medium
[ Michael Biebl ]
* Upload to unstable
* Revert "d/t/timedated: use /bin/bash to work around job handling issue in
dash"
[ Balint Reczey ]
* debian/
There may be other children of the script due to autopkgtest machinery
and they exit after the script exited. (LP: #1904406)
systemd (247.1-1) experimental; urgency=medium
* New upstream version 247.1
systemd (247-1) experimental; urgency=medium
* New upstream version 247
* Rebase patches
* Update symbol versions for the v247 release
systemd (247~...
Changed in systemd (Ubuntu Hirsute): | |
status: | Fix Committed → Fix Released |
Hello Kleber, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in systemd (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
tags: | added: verification-needed verification-needed-focal |
Chris Halse Rogers (raof) wrote : | #8 |
Hello Kleber, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in systemd (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
tags: | added: verification-needed-bionic |
Chris Halse Rogers (raof) wrote : | #9 |
Hello Kleber, or anyone else affected,
Accepted systemd into groovy-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in systemd (Ubuntu Groovy): | |
status: | In Progress → Fix Committed |
tags: | added: verification-needed-groovy |
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (systemd/245.4-4ubuntu3.4) | #10 |
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.4) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
linux-hwe-
netplan.
apt/2.0.2ubuntu0.2 (armhf)
munin/2.
gvfs/1.
prometheus-
lxc/1:4.
indicator-
pyudev/
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (systemd/237-3ubuntu10.44) | #11 |
All autopkgtests for the newly accepted systemd (237-3ubuntu10.44) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
linux-azure-
munin/2.
gvfs/1.
libvirt/
apt/1.6.12ubuntu0.2 (armhf)
netplan.
linux-hwe-
openssh/
corosync/
nut/2.7.
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (systemd/246.6-1ubuntu1.1) | #12 |
All autopkgtests for the newly accepted systemd (246.6-1ubuntu1.1) for groovy have finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.
prometheus/
netplan.
flatpak/1.8.2-1 (arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
Dan Streetman (ddstreet) wrote : | #13 |
The test-cap-list test no longer fails when running the autopkgtest suite with 5.8 kernel:
https:/
that verifies for focal. As mentioned in the description [scope], the test case fix was backported there to prevent build failures if the lp build farm ever updates to the 5.8 kernel, but since that situation isn't trivial to reproduce (and since this is a testcase only fix and is verified above in focal), i'm using the focal verification to assume verification of bionic as well. Groovy similarly is hard to verify since this would require systemd in g to be *built* with older kernel headers but then tested with newer running kernel, so I'm assuming focal verification covers groovy as well.
tags: |
added: verification-done verification-done-bionic verification-done-focal verification-done-groovy removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy |
Launchpad Janitor (janitor) wrote : | #14 |
This bug was fixed in the package systemd - 246.6-1ubuntu1.1
---------------
systemd (246.6-1ubuntu1.1) groovy; urgency=medium
[ Dan Streetman ]
* d/t/boot-smoke: update test to avoid false negatives
(LP: #1892358)
https:/
* d/t/boot-
(LP: #1892358)
https:/
* d/t/systemd-fsckd: rewrite test to try to fix false negatives
(LP: #1892358)
https:/
* d/p/lp1905044-
test: use cap_last_cap() instead of capability_
(LP: #1905044)
https:/
* d/p/lp1907306/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
Send correct number of dhcpv4 renew and rebind requests
(LP: #1907306)
https:/
* d/p/lp1902960-
Run net_setup_link on 'change' uevents (LP: #1902960)
https:/
* d/t/root-unittests:
Remove any corrupt journal files (LP: #1881947)
https:/
[ Balint Reczey ]
* d/t/systemd-fsckd: Plymouth-start stays active in 20.10 and later
(LP: #1908067)
https:/
-- Dan Streetman <email address hidden> Wed, 06 Jan 2021 15:40:39 -0500
Changed in systemd (Ubuntu Groovy): | |
status: | Fix Committed → Fix Released |
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
Launchpad Janitor (janitor) wrote : | #16 |
This bug was fixed in the package systemd - 245.4-4ubuntu3.4
---------------
systemd (245.4-4ubuntu3.4) focal; urgency=medium
* d/p/lp1905245/
d/p/
d/p/
- print number of unknown capabilities instead of failing
(LP: #1905245)
https:/
* d/p/lp1890448-
Add EliteBook to use micmute hotkey (LP: #1890448)
https:/
* d/extra/
suppress output of cmp command in dhclient hook (LP: #1878955)
https:/
* d/p/lp1905044-
test: use cap_last_cap() instead of capability_
(LP: #1905044)
https:/
* d/p/lp1903300/
d/p/
d/p/
set vxlan multicast group when specified (LP: #1903300)
https:/
* d/p/lp1907306/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
d/p/
Send correct number of dhcpv4 renew and rebind requests
(LP: #1907306)
https:/
* d/p/lp1902960-
Run net_setup_link on 'change' uevents (LP: #1902960)
https:/
* d/t/root-unittests:
Remove any corrupt journal files (LP: #1881947)
https:/
-- Dan Streetman <email address hidden> Wed, 06 Jan 2021 15:47:39 -0500
Changed in systemd (Ubuntu Focal): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #17 |
This bug was fixed in the package systemd - 237-3ubuntu10.44
---------------
systemd (237-3ubuntu10.44) bionic; urgency=medium
* d/extra/
suppress output of cmp command in dhclient hook (LP: #1878955)
https:/
* d/p/lp1905044/
d/p/
test: use cap_last_cap() instead of capability_
(LP: #1905044)
https:/
* d/p/lp1905245/
print number of unknown capabilities instead of failing
(LP: #1905245)
https:/
* d/p/lp1907306/
d/p/
d/p/
d/p/
d/p/
d/p/
Send correct number of dhcpv4 renew and rebind requests
(LP: #1907306)
https:/
* d/t/root-unittests:
Remove any corrupt journal files (LP: #1881947)
https:/
-- Dan Streetman <email address hidden> Wed, 06 Jan 2021 16:04:25 -0500
Changed in systemd (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
likely same as bug 1905245