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.
Bug 1908275 - `systemctl show xxx` throws "Failed to parse bus message: Invalid argument"
Summary: `systemctl show xxx` throws "Failed to parse bus message: Invalid argument"
Keywords:
Status: CLOSED DUPLICATE of bug 1901449
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 8.3
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks: 1908773
TreeView+ depends on / blocked
 
Reported: 2020-12-16 09:58 UTC by Rainer Beyel
Modified: 2023-01-30 11:14 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-05 09:47:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CentOS 17747 0 None None None 2020-12-23 19:51:16 UTC
Red Hat Bugzilla 1853736 0 unspecified CLOSED systemctl show service fails with "Failed to parse bus message: Invalid argument" 2021-02-22 00:41:40 UTC

Internal Links: 1853736

Description Rainer Beyel 2020-12-16 09:58:36 UTC 
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",
     ...
Comment 1 Tim Jackson 2020-12-17 10:14:43 UTC 
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
Comment 2 Sandro Bonazzola 2020-12-20 18:50:03 UTC 
Raising severity to high since this breaks major flows in layered products.
Comment 3 Yedidyah 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.
Comment 4 Stef Walter 2020-12-21 12:51:50 UTC 
Miro, is this the same bug you saw affect the Testing Farm Service?
Comment 5 Zbigniew Jędrzejewski-Szmek 2020-12-21 13:29:02 UTC 
> Hello Zbigniew, can you please share current status of this bug on Stream?

Sorry, I have no idea about Stream.
Comment 6 Stef Walter 2020-12-21 14:23:57 UTC 
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 7 lingwangneuraleng 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.
Comment 8 David Tardon 2021-01-05 09:47:37 UTC 

*** This bug has been marked as a duplicate of bug 1901449 ***
Comment 9 Akemi Yagi 2021-01-05 18:46:57 UTC 
This bug was closed as a duplicate of bug 1901449 but the linked bug is closed. Please make it publicly accessible.
Note You need to log in before you can comment on or make changes to this bug.