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`
*** Bug 1853407 has been marked as a duplicate of this bug. ***
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.
https://github.com/systemd/systemd/pull/16420 (A rebuild will fix this too.)
Built in rawhide.
FEDORA-2020-2faf839786 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2faf839786
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.
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.
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?
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?
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>"
this is still happening on centos stream, can we fix it there too? https://bugzilla.redhat.com/show_bug.cgi?id=1910430
This is tracked for CentOS Stream in https://bugzilla.redhat.com/show_bug.cgi?id=1908275