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:
Currently, it is not really obvious that systemd didn't connect properly to dbus-daemon during system boot. When systemd is not connected to the dbus then some of its APIs are not available and system is overall in the degraded state. Right now we do the very poor job when it comes to reporting this situation.

Version-Release number of selected component (if applicable):
systemd-219-42.el7_4.7

How reproducible:
rarely

Steps to Reproduce:
1. This issue is hard to reproduce, but when it happens it is even harder to recognize from the log that it occurred.

Actual results:
systemd is not connected to dbus, there is no clear indication in the log

Expected results:
systemd is not connected to dbus, but it is possible to recognize the issue by looking at the system log

Additional info:
https://github.com/systemd/systemd/pull/7851

fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/191 -> post

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0711