Bug 1756912

Summary: [FAILED] Failed to start D-Bus System Message Bus.
Product: [Fedora] Fedora Reporter: David Hildenbrand <dhildenb>
Component: dbusAssignee: Colin Walters <walters>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 31CC: amigadave, caillon+fedoraproject, cohuck, dhorak, gnome-sig, john.j5live, lpoetter, mclasen, rhughes, rstrode, sandmann, tgunders, walters
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-11 13:15:56 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 David Hildenbrand 2019-09-30 08:09:19 UTC 
Description of problem:

The system services
 [DEPEND] Dependency failed for Login Service.
 [DEPEND] Dependency failed for Network Manager
Keep failing in a loop with "[FAILED] Failed to start D-Bus System Message Bus."

The system is basically unusable.


Version-Release number of selected component (if applicable): Fedora-Cloud-Base-31_Beta-1.1.s390x.qcow2 as well as Fedora-Cloud-Base-31-20190928.n.0.s390x.qcow2


How reproducible: 100%


Steps to Reproduce:
1. Download Fedora-Cloud-Base-31_Beta-1.1.s390x.qcow2
2. /usr/libexec/qemu-kvm -smp 2 -m 1G -nographic -hda Fedora-Cloud-Base-31_Beta-1.1.s390x.qcow2


Actual results: OS boots but there is an error loop. D-BUS does not work, making the OS basically unusable.


Expected results: OS boots without error-loop. and can be used.


Additional info: Can also be reproduced using upstream QEMU TCG:

s390x-softmmu/qemu-system-s390x -nographic -m 8G -smp 4 -hda Fedora-Cloud-Base-31_Beta-1.1.s390x.qcow2
Comment 1 David Hildenbrand 2019-10-01 08:36:01 UTC 
This also happens when installing from ISO and booting into the freshly-installed OS. The installation works just fine, though.
Comment 2 Dan Horák 2019-10-11 13:15:56 UTC 
Will be fixed in F-31 GA with a selinux policy update.

*** This bug has been marked as a duplicate of bug 1746413 ***