Bug 1541061

Summary:	systemd should provide clear indication in the system log that connection to system bus failed
Product:	Red Hat Enterprise Linux 7	Reporter:	Michal Sekletar <msekleta>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	fsumsal, systemd-maint-list, thozza
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	systemd-219-54.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 11:25:34 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:

Description Michal Sekletar 2018-02-01 15:45:33 UTC

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

Comment 4 Lukáš Nykrýn 2018-02-06 14:26:23 UTC

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

Comment 9 errata-xmlrpc 2018-04-10 11:25:34 UTC

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