Bug 1908275
| Summary: | `systemctl show xxx` throws "Failed to parse bus message: Invalid argument" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Rainer Beyel <rbeyel> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED DUPLICATE | QA Contact: | Frantisek Sumsal <fsumsal> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | ajb, bstinson, carl, didi, dtardon, farrotin, jwboyer, kdreyer, lingwangneuraleng, markus.falb, msekleta, mvadkert, ngompa13, reupke, rpm, sbonazzo, stefw, systemd-maint-list, toracat, zbyszek |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-01-05 09:47:37 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1908773 | ||
I see this with a fully updated CentOS 8 Stream VM and the following: kernel-4.18.0-257.el8.x86_64 systemd-239-43.el8.x86_64 It prevents any Ansible job that tries to manage a systemd service running properly (failing with "Service is in unknown state", as described in https://github.com/ansible/ansible/issues/71528 ). In other words, likely breaks many common use cases of Ansible with CentOS Stream as a target. Rolling the kernel back to 4.18.0-257.el8.x86_64 successfully works around it. It is fixed upstream in systemd; presumably CentOS Stream needs a new systemd or at least a backport of this patch: https://github.com/ansible/ansible/pull/72337 Raising severity to high since this breaks major flows in layered products. Hello Zbigniew, can you please share current status of this bug on Stream? I see it's solved in Fedora (bug 1853736, bug 1878530, not sure which, or perhaps both). Are there any known workarounds? Thanks. Miro, is this the same bug you saw affect the Testing Farm Service? > Hello Zbigniew, can you please share current status of this bug on Stream?
Sorry, I have no idea about Stream.
Hey Michael, do you think this is an issue in the RHEL nightlies (from which CentOS Stream syncs)? If not, and this problem is no longer visible in RHEL nightlies ... then it would be indicative of a bug in the syncing to CentOS Stream itself, and we should reassign to Brian Stinson. https://bugzilla.redhat.com/show_bug.cgi?id=1910430 The problem does not present on centos8 but centos stream. Because new kernels introduce new values. The systemd package (systemd-239-43.el8) need to be rebuild against new kernels of centos stream: `4.18.0-257.el8` or `4.18.0-259.el8`. ``` systemctl show -p CapabilityBoundingSet bash Failed to parse bus message: Invalid argument ``` However, the systemd srpm cannot be rebuild via mock: https://bugzilla.redhat.com/show_bug.cgi?id=1910425 Currently this bug prevent us from running ansible playbook with systemd module, to work around one has to replace tasks depending on systemd module by shell/command module, which is quite amount of work. *** This bug has been marked as a duplicate of bug 1901449 *** This bug was closed as a duplicate of bug 1901449 but the linked bug is closed. Please make it publicly accessible. |
Description of problem: From a previous bugzilla [1], I suspect this to be the cause for my failing ansible runs [2] Version-Release number of selected component: CentOS 8 Stream, updated today Actual results: # systemctl show rsyslog > /dev/null ; echo $? Failed to parse bus message: Invalid argument 1 Expected results: # systemctl show rsyslog > /dev/null ; echo $? 0 Additional info: 1) systemctl show service fails with "Failed to parse bus message: Invalid argument" https://bugzilla.redhat.com/show_bug.cgi?id=1853736 2) $ ansible host01 -m service -a'name=rsyslog state=started' ... "msg": "Service is in unknown state", ...