Bug 1853736

Summary: systemctl show service fails with "Failed to parse bus message: Invalid argument"
Product: [Fedora] Fedora Reporter: David Sastre Medina <david.sastre>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: fboucher, jpena, kdreyer, lingwangneuraleng, lnykryn, msekleta, orion, pasteur, redhat-bugzilla, redhat, ssahani, s, systemd-maint, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-246~rc2-1.fc33 systemd-245.7-1.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-30 18:56:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
output of strace none

Description David Sastre Medina 2020-07-03 17:55:18 UTC
Created attachment 1699877 [details]
output of strace

Description of problem:

`systemctl show` errors out and does not provide complete information.
As a result, anything dependent on this output is not operational (e.g. ansible systemd module)

Version-Release number of selected component (if applicable):

# systemctl --version
systemd 245 (v245.6-2.fc33)
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified

How reproducible:

Always

Steps to Reproduce:

1.run `systemctl show sshd`

Actual results:

# systemctl show sshd | grep ActiveState
Failed to parse bus message: Invalid argument

Expected results:

# systemctl show firewalld | grep ActiveState
ActiveState=active

Additional info:

Attached output of `strace --string-limit=15000 -o /tmp/systemd_bus.txt systemctl show sshd`

Comment 1 Kevin Fenzi 2020-07-04 18:27:43 UTC
*** Bug 1853407 has been marked as a duplicate of this bug. ***

Comment 2 Zbigniew Jędrzejewski-Szmek 2020-07-09 20:30:39 UTC
Yeah, I can see reproduce this. It's failing on CapabilityBoundingSet because it doesn't know how
to display cap_bpf. cap_bpf was added recently. Recompiling systemd against the new headers is
enough to fix the issue, but to avoid a repeat the next time a new capability is added, the code
needs to be handle unknown capabilities gracefully.

Comment 3 Zbigniew Jędrzejewski-Szmek 2020-07-09 21:26:40 UTC
https://github.com/systemd/systemd/pull/16420

(A rebuild will fix this too.)

Comment 4 Zbigniew Jędrzejewski-Szmek 2020-07-24 08:18:47 UTC
Built in rawhide.

Comment 5 Fedora Update System 2020-07-27 09:52:19 UTC
FEDORA-2020-2faf839786 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2faf839786

Comment 6 Fedora Update System 2020-07-28 15:19:37 UTC
FEDORA-2020-2faf839786 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-2faf839786`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2faf839786

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-07-30 18:56:29 UTC
FEDORA-2020-2faf839786 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Javier Peña 2020-09-02 14:11:58 UTC
I am getting the same error when running a centos:8 systemd-enabled container on a Fedora 32 host. I guess this might be due to the systemd version running on CentOS 8, are there any plans to backport the fix to that systemd release, too?

Comment 9 Orion Poplawski 2020-09-17 14:44:45 UTC
I'm seeing this with:

systemd-243.8-1.fc31.x86_64
kernel-5.8.9-101.fc31.x86_64

Can we get it fixed there as well?

Comment 10 Ken Dreyer (Red Hat) 2020-10-27 15:00:19 UTC
I'm seeing this problem when I run systemd inside a centos:8 container on a Fedora 32 host. Ansible's systemd module fails with "Service is in unknown state" because it cannot parse "systemctl show <servicename>"

Comment 11 lingwangneuraleng 2021-01-04 15:28:17 UTC
this is still happening on centos stream, can we fix it there too?

https://bugzilla.redhat.com/show_bug.cgi?id=1910430

Comment 12 Ken Dreyer (Red Hat) 2021-01-04 21:52:33 UTC
This is tracked for CentOS Stream in https://bugzilla.redhat.com/show_bug.cgi?id=1908275