Bug 735355

Summary: DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Product: [Fedora] Fedora Reporter: Martin Banas <mbanas>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: high    
Version: rawhideCC: anaconda-maint-list, bbaude, jonathan, mbanas, pknirsch, rvykydal, vanmeeuwen+fedora
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: powerpc   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-07 16:51:19 UTC Type: ---
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
traceback from anaconda none

Description Martin Banas 2011-09-02 13:21:36 UTC
Created attachment 521227 [details]
traceback from anaconda

Description of problem:
DBusException after discovering all disks during installation of Fedora-20110902-ppc64-netinst.iso

Version-Release number of selected component (if applicable):
anaconda 16.16
Fedora-20110902-ppc64-netinst.iso

How reproducible:
always

Steps to Reproduce:
1. get kernel + initrd from iso above, copy to /boot
2. copy LiveOS folder to /boot
3. add following to /boot/etc/yaboot.conf:
image=/vmlinuz
        label=install
        initrd=/initrd.img
        append="root=live:/dev/sda2 serial rdshell"

5. reboot
6. proceed to stage2
7. After the message that my system cannot be upgraded I see this traceback (previously RHEL6 installed)

Actual results:
DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

See full traceback in attachment

Expected results:
No traceback, successfully proceed to next step

Additional info:
Happens on ibm power7

Comment 1 Martin Banas 2011-09-02 13:28:05 UTC
Seems to be a dup of 733680

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

Comment 2 Radek Vykydal 2011-09-08 07:58:30 UTC
I am putting back to assigned until more investigation / retesting with newer compose happens, see https://bugzilla.redhat.com/show_bug.cgi?id=733680#c8.

Are you able to watch console (tty3) message from systemctl call (as in the second paragraph of https://bugzilla.redhat.com/show_bug.cgi?id=733680#c2)? That could give some clue.

Comment 3 Phil Knirsch 2012-01-13 19:52:02 UTC
Please retest with Fedora 16 for PPC GA version.

Thanks & regards, Phil

Comment 4 Brent Baude 2013-02-07 16:51:19 UTC
Closing this bug for lack of response.  Please re-open a new bug in F18 if it fails there.

Comment 5 Martin Banas 2013-02-08 07:27:01 UTC
Sorry, I somehow missed this one. Retested on F18 final and this doesn't happen on power7 anymore.