Bug 987714

Summary: Failed to get D-Bus connection: No connection to service manager.
Product: Red Hat Enterprise Linux 7 Reporter: Brian Lane <bcl>
Component: systemdAssignee: systemd-maint
Status: CLOSED INSUFFICIENT_DATA QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: bcl, harald, msekleta, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-18 15:17:15 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:
Attachments:
Description Flags
journalctl output with rd.debug none

Description Brian Lane 2013-07-24 00:20:06 UTC 
Description of problem:
Trying to debug a driver-update disk problem with 7/22 nightly boot.iso

Version-Release number of selected component (if applicable):
Unknown.

How reproducible:
Always.

Steps to Reproduce:
1. Boot with a dd iso attached as a disk and pass inst.dd=/dev/sda rd.debug
2. Observe attempt to start driver-updates fail

This works on F19, and on earlier RHEL7 composes (this is related to bug 987513, I've asked for the version he used).
Comment 1 Brian Lane 2013-07-24 00:23:00 UTC 
Created attachment 777526 [details]
journalctl output with rd.debug

The relevant section can be found by searching for "Starting Driver Update Disk"

Jul 23 23:51:32 localhost dracut: Starting Driver Update Disk Service on tty1
Jul 23 23:51:32 localhost dracut: ///lib/dracut/hooks/pre-trigger/40-driver-updates.sh@25(source): echo /dev/sda
Jul 23 23:51:32 localhost dracut: ///lib/dracut/hooks/pre-trigger/40-driver-updates.sh@26(source): info 'Starting Driver Update Disk Service on tty1'
Jul 23 23:51:32 localhost dracut: //lib/dracut-lib.sh@417(info): check_quiet
Jul 23 23:51:32 localhost dracut: //lib/dracut-lib.sh@397(check_quiet): '[' -z yes ']'
Jul 23 23:51:32 localhost dracut: //lib/dracut-lib.sh@418(info): echo '<30>dracut: Starting Driver Update Disk Service on tty1'
Jul 23 23:51:32 localhost dracut: //lib/dracut-lib.sh@419(info): '[' yes '!=' yes ']'
Jul 23 23:51:32 localhost dracut: ///lib/dracut/hooks/pre-trigger/40-driver-updates.sh@27(source): systemctl start driver-updates
Jul 23 23:51:32 localhost dracut: Failed to get D-Bus connection: No connection to service manager.
Jul 23 23:51:32 localhost dracut: ////lib/dracut/hooks/pre-trigger/40-driver-updates.sh@28(source): systemctl -p ExecMainStatus show driver-updates
Jul 23 23:51:32 localhost dracut: Failed to get D-Bus connection: No connection to service manager.
Jul 23 23:51:32 localhost dracut: DD status=
Jul 23 23:51:32 localhost dracut: ///lib/dracut/hooks/pre-trigger/40-driver-updates.sh@28(source): status=
Jul 23 23:51:32 localhost dracut: ///lib/dracut/hooks/pre-trigger/40-driver-updates.sh@29(source): info 'DD status='
Jul 23 23:51:32 localhost dracut: //lib/dracut-lib.sh@417(info): check_quiet
Jul 23 23:51:32 localhost dracut: //lib/dracut-lib.sh@397(check_quiet): '[' -z yes ']'
Jul 23 23:51:32 localhost dracut: //lib/dracut-lib.sh@418(info): echo '<30>dracut: DD status='
Jul 23 23:51:32 localhost dracut: //lib/dracut-lib.sh@419(info): '[' yes '!=' yes ']'
Comment 3 Brian Lane 2013-07-24 16:41:33 UTC 
The boot.iso from RHEL-7.0-20130710.n.0 is working correctly, so whatever changed was after that.
Comment 4 Harald Hoyer 2013-07-30 08:57:33 UTC 
In the initramfs there is no D-Bus. But I agree, systemctl should fall back to non-D-BUS communication here!
Comment 5 Harald Hoyer 2013-07-30 10:22:58 UTC 
err... in the latest boot.iso it seems like systemd is not even included in the initramfs.
Comment 6 Harald Hoyer 2013-07-30 11:39:54 UTC 
(In reply to Harald Hoyer from comment #5)
> err... in the latest boot.iso it seems like systemd is not even included in
> the initramfs.

Can you confirm that?
Comment 7 RHEL Program Management 2014-03-22 06:43:28 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.