"Failed to parse bus message: Invalid argument" with Linux 5.8
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| systemd (Ubuntu) |
Undecided
|
Unassigned | ||
| Bionic |
High
|
Dan Streetman | ||
| Focal |
High
|
Dan Streetman |
Bug Description
[impact]
newer kernels introduced a new capability, and existing systemd doesn't have the name mapping for the new cap (since the mapping table is generated at systemd compile time), so it fails when trying to map the capability to a user-facing name, which causes failure when running commands like 'systemctl show'
[test case]
install a focal system, and install the 5.8 (or newer) kernel, e.g. from linux-generic-
Find any service that does not specify its CapabilityBound
ubuntu@
Failed to parse bus message: Invalid argument
the command should correctly show the value, e.g.:
$ systemctl show -p CapabilityBound
CapabilityBound
[regression potential]
a regression would likely occur while systemd is parsing or printing or otherwise handling kernel capabilities. A regression could happen when running systemd commands, such as systemctl, or when pid1 is managing services.
[scope]
this is needed only in focal and bionic.
This is fixed upstream by PR 16424:
https:/
which was first included in v246, so this is already fixed in groovy and later.
This was introduced upstream in systemd by commit 52610b020c077ee
This bug will reproduce on any system running under the 5.8 kernel, with the new capability, if the systemd binary was compiled with kernel headers that do not include the new capability. This means this is reproducable on bare-metal/vm instances running 5.8, as well as containers on hosts running 5.8. Therefore, while bionic may not ever receive a new kernel with added capability, it still needs to be patched to avoid the bug on a bionic container running on a host with the 5.8 kernel.
[other info]
there is a testcase-only related bug 1905044
[original description]
When I run `systemctl show myservice.service`, I get the following error message:
Failed to parse bus message: Invalid argument
systemd version: 245.4-4ubuntu3.3
linux version: 5.8.0-29-generic #31~20.04.1-Ubuntu (From linux-generic-
This is a bug that has been fixed in Debian. See https:/
Please can we port the fix to the ubuntu 20.04 version.
lotuspsychje (lotuspsychje) wrote : | #1 |
tags: | added: rls-bb-incoming rls-ff-incoming |
description: | updated |
Changed in systemd (Ubuntu): | |
status: | New → Fix Released |
description: | updated |
Changed in systemd (Ubuntu Focal): | |
assignee: | nobody → Dan Streetman (ddstreet) |
importance: | Undecided → Medium |
status: | New → In Progress |
tags: | added: fr-963 |
tags: | removed: rls-bb-incoming rls-ff-incoming |
Changed in systemd (Ubuntu Bionic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
importance: | Undecided → Medium |
status: | New → In Progress |
description: | updated |
description: | updated |
Stéphane Graber (stgraber) wrote : | #3 |
Now that we have the 5.8 kernel in HWE for focal, all my servers are hitting this, both on metal and in containers. This causes things like "systemctl show" to show an error as well as partial data.
It really feels like this should have been fixed before the rollout of the 5.8 kernel through HWE...
Dan Streetman (ddstreet) wrote : | #4 |
Sorry for the delay; the patched systemd is in the upload queue:
https:/
Changed in systemd (Ubuntu Focal): | |
importance: | Medium → High |
Changed in systemd (Ubuntu Bionic): | |
importance: | Medium → High |
description: | updated |
Hello Gary, 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 : | #6 |
Hello Gary, 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 |
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!
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!
Dan Streetman (ddstreet) wrote : | #9 |
focal host reproduction:
root@lp1905245-f:~# uname -a
Linux lp1905245-f 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
root@lp1905245-f:~# dpkg -l systemd|grep systemd
ii systemd 245.4-4ubuntu3.3 amd64 system and service manager
root@lp1905245-f:~# systemctl show -p CapabilityBound
Failed to parse bus message: Invalid argument
root@lp1905245-f:~# echo $?
1
focal container repro:
root@lp1905245-f:~# lxc shell focal
root@focal:~# dpkg -l systemd|grep systemd
ii systemd 245.4-4ubuntu3.3 amd64 system and service manager
root@focal:~# systemctl show -p CapabilityBound
Failed to parse bus message: Invalid argument
root@focal:~# echo $?
1
bionic container repro:
root@lp1905245-f:~# lxc shell bionic
root@bionic:~# dpkg -l systemd|grep systemd
ii systemd 237-3ubuntu10.43 amd64 system and service manager
root@bionic:~# systemctl show -p CapabilityBound
Failed to parse bus message: Invalid argument
root@bionic:~# echo $?
1
focal host verification:
root@lp1905245-f:~# dpkg -l systemd|grep systemd
ii systemd 245.4-4ubuntu3.4 amd64 system and service manager
root@lp1905245-f:~# systemctl show -p CapabilityBound
CapabilityBound
root@lp1905245-f:~# echo $?
0
focal container verification:
root@focal:~# dpkg -l systemd|grep systemd
ii systemd 245.4-4ubuntu3.4 amd64 system and service manager
root@focal:~# systemctl show -p CapabilityBound
CapabilityBound
root@focal:~# echo $?
0
bionic container verification:
root@bionic:~# dpkg -l systemd|grep systemd
ii systemd 237-3ubuntu10.44 amd64 system and service manager
root@bionic:~# systemctl show -p CapabilityBound
CapabilityBound
root@bionic:~# echo $?
0
tags: |
added: verification-done verification-done-bionic verification-done-focal removed: verification-needed verification-needed-bionic verification-needed-focal |
Launchpad Janitor (janitor) wrote : | #10 |
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 |
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 : | #12 |
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 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1905245
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.