Bug 928287

<msivak> can you try it with qxl driver?

I tried a minimal install in English twice using

ionice -c 3 qemu-kvm -enable-kvm -m 2048M -smp 4 -drive file=./Fedora-19-Alpha-TC2-x86_64-DVD.iso.qcow2,index=0,media=disk,cache=unsafe -localtime -serial file:/tmp/qemu-Fedora-19-Alpha-TC2-x86_64-DVD.iso.qcow2-output.log -name Fedora-19-Alpha-TC2-x86_64-DVD.iso.qcow2 -cdrom /local/mfabian/iso/Fedora-19-Alpha-TC2/Fedora-19-Alpha-TC2-x86_64-DVD.iso -boot c -vga qxl -display sdl -net nic -net user,hostname=Fedora-19-Alpha-TC2-x86_64-DVD.iso.qcow2,hostfwd=tcp::5560-:22 -monitor stdio -usb

and it worked both times.

Created attachment 717041 [details]
/tmp/syslog

<vpodzime> mfabian: can you get the /tmp/syslog file in case of another crash?

Reproduce the crash and attached syslog.

Created attachment 717042 [details]
/tmp/syslog

<vpodzime> mfabian: can you get the /tmp/syslog file in case of another crash?

Reproduce the crash and attached syslog.

from the end of the /tmp/syslog file:
> 11:49:08,750 NOTICE dbus: [system] Successfully activated service org.freedesktop.locale1'
> 11:49:08,751 INFO systemd: Started Locale Service.

I've seen some crashes happening when Anaconda tried to talk to systemd-localed over DBus. I guess this is the same case.

It seems to happen with all video drivers, that it worked twice with qxl
(comment#2) was just luck.

bug#928838 might be a duplicate.

*** Bug 928838 has been marked as a duplicate of this bug. ***

Mike, could you please try this updates image?

http://vpodzime.fedorapeople.org/928287_updates.img

(by adding "updates=http://vpodzime.fedorapeople.org/928287_updates.img" to command line)

This crash happens when Anaconda tries to talk to systemd-localed over DBus from a non-main thread.

This happened to me with TC3 net install on bare metal (bug 928838).

(In reply to comment #9)
> This happened to me with TC3 net install on bare metal (bug 928838).
It is not not specific to virtual machines. But it is probably some kind of race condition because it doesn't happen every time so maybe it happens on virtual machines more often.

If the installed system is actually functional, then the install has been completed, and I'd probably be -1 on this as a blocker...

(In reply to comment #11)
> If the installed system is actually functional, then the install has been
> completed, and I'd probably be -1 on this as a blocker...

The installed system is not functional, when rebooting after the screen becomes
black, the system does not boot.

(In reply to comment #8)
> Mike, could you please try this updates image?
> 
> http://vpodzime.fedorapeople.org/928287_updates.img
> 
> (by adding "updates=http://vpodzime.fedorapeople.org/928287_updates.img" to
> command line)
> 
> This crash happens when Anaconda tries to talk to systemd-localed over DBus
> from a non-main thread.

I tried it 5 times with the above updates images and it worked every time.

Then I tried again 2 times without the updates images and the error was there.

So I think the update it helps.

(I tried with Fedora-19-Alpha-TC3-x86_64-DVD.iso)

Yep,  I can confirm the fix as well.

Thanks a lot for testing, guys. Unfortunately the fix in the updates.img was not a nice thing to do. But it proved where the problem lies. Could you please try a new updates.img with a nicer and more versatile patch [1]? It works for me. If it also works in your cases, we will have a winner. :) Otherwise I'll go with the previous fix for Alpha and think about something better for later versions.

[1] http://vpodzime.fedorapeople.org/928287_updates_new.img

(In reply to comment #15)
> Thanks a lot for testing, guys. Unfortunately the fix in the updates.img was
> not a nice thing to do. But it proved where the problem lies. Could you
> please try a new updates.img with a nicer and more versatile patch [1]? It
> works for me. If it also works in your cases, we will have a winner. :)
> Otherwise I'll go with the previous fix for Alpha and think about something
> better for later versions.
> 
> [1] http://vpodzime.fedorapeople.org/928287_updates_new.img

I tried this new fix Fedora-19-Alpha-TC3-x86_64-DVD.iso and it
worked for me 2 times.

928287_updates_new.img also worked for me.

Great! Thanks a lot, guys! I've posted patches to anaconda-patches.

(In reply to comment #11)
> If the installed system is actually functional, then the install has been
> completed, and I'd probably be -1 on this as a blocker...

I have hit this problem as well, hard rebooted the computer, and the system boots (it was a minimal install), but the root password is different from what I've set. It probably didn't sync properly. I guess the system might be in a somewhat broken state.

(In reply to comment #19)
> I have hit this problem as well, hard rebooted the computer, and the system
> boots (it was a minimal install), but the root password is different from
> what I've set. It probably didn't sync properly. I guess the system might be
> in a somewhat broken state.

According to Vratislav the same code is also run before installing the booloader, so sometimes even the bootloader is not installed.

Discussed at 2013-04-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-03/f19alpha-blocker-review-4.2013-04-03-16.01.log.txt . Accepted as a blocker per criterion "When using the dedicated installer images, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces." - this criterion is used for showstopper bugs like this, as the install did not 'complete'.

Can we please have a new build of anaconda with this fix in it ASAP, anaconda team? bcl, sorry I asked for a new build last night without specifying that we need this fix in it :(

*** Bug 947666 has been marked as a duplicate of this bug. ***

I only saw this behavior when trying to use TC3 Anaconda to install Fedora 18 mirror. This happened on physical HW vs KVM also.

Vratislav, could you do an updates.img against TC4 with your fix? I had to request TC4 without this fix, but it'd be good if we could use an updates.img to get around it for further testing.

anaconda-19.16-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/anaconda-19.16-2.fc19

saw this on dd USB TC4 netinstallx86_64 to MacBookPro i7 EFI boot. Screen went black at end of install

Live TC4 x86_64 install on bare metal with anaconda-19.16-2.fc19 succeeded . :)

(In reply to comment #24)
> Vratislav, could you do an updates.img against TC4 with your fix? I had to
> request TC4 without this fix, but it'd be good if we could use an
> updates.img to get around it for further testing.

http://vpodzime.fedorapeople.org/928287_updates_tc4.img

TC5 should have a new anaconda with the patch applied.

I tried F19a TC5 on a physical system usually ended in the black screen (and non-bootable TC3/TC4) and installed ok. No black screen. I was able to finally install F19a TC5 on that system.

Marking as VERIFIED, please upkarma the anaconda update, thanks!

(BTW for the record it seems the crashes were mostly (only?) happening
with smp ie on systems with multiple cpu's.)

(In reply to comment #31)
> (BTW for the record it seems the crashes were mostly (only?) happening
> with smp ie on systems with multiple cpu's.)
Thanks for the additional info it may be a huge help in some future cases, because I'm afraid this can happen in any other project using Python dbus module and multiple threads.

anaconda-19.16-2.fc19, python-meh-0.22-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.