Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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",
...
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.
Comment 3Yedidyah Bar David
2020-12-21 10:39:08 UTC
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.
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.
Comment 7lingwangneuraleng
2021-01-05 07:14:53 UTC
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.
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", ...