Bug 862801

Created attachment 620980 [details]
anaconda.log

Created attachment 620981 [details]
ifcfg.log

Created attachment 620982 [details]
packaging.log

Created attachment 620983 [details]
program.log

Created attachment 620984 [details]
storage.log

Proposing as a Beta blocker per (Alpha) criterion: "The installer must be able to complete an installation using the text, graphical and VNC installation interfaces."

Did you boot this install with selinux=0 or did you disable selinux in some other way?

saw this on f18-Beta-TC1 DVD and netinstall CD's
Install to USB HD
System booted fine afterwards

Discussed at 2012-10-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-03/f18-beta-blocker-review-2.2012-10-03-16.00.log.txt . There are indications that more than one system has hit this - I think I hit it myself once, but don't recall the details - but we don't yet have it nailed down. There's a possibility this affects enough systems to be a blocker, so we are leaving it open to collect more data and re-evaluate later.

note that we think satellit's case sounds more like https://bugzilla.redhat.com/show_bug.cgi?id=860791 than this bug.

(In reply to comment #7)
> Did you boot this install with selinux=0 or did you disable selinux in some
> other way?

No, I did not.

Can we also get the syslog?

Might be good to retest with 18.12 in Beta TC2.

This seems to hit more people:
http://lists.fedoraproject.org/pipermail/test/2012-October/110648.html

I had already destroyed the F18 Beta TC2 VM as networking was not working and somehow /sbin/ifconfig was missing (?). I did a reinstall and got the same systems, anaconda hanging at 'Configuring installed system'.


I'll attach syslog.

Created attachment 622284 [details]
syslog (KVM install)

Created attachment 622287 [details]
all logs tarred for good measure

Installed gnome3.6.0 with F18_Beta-TC2-x86_64 DVD last night
Anaconda install hung with "Configuring installed system"
after 1 hour I powered off system. Install booted to firstboot and gdm login fine
_ missing signal for reboot message in anaconda could be the the problem?
FYI https://bugzilla.redhat.com/show_bug.cgi?id=860791 occured at the same point in install in TC1 is this related?

Created attachment 622807 [details]
Logs from Lenovo ThinkPad X230

Here are some logs from real hardware. Lenovo ThinkPad X230 (Model 2325-2DG).
Tested with Beta TC2.
Also tested with anaconda 18.13 from koji. Same problem but did not keep the logs.

I've encountered this too, on a bare metal machine with Beta TC2. Adding logs.

Created attachment 623378 [details]
anaconda.log

Created attachment 623379 [details]
program.log

Created attachment 623380 [details]
storage.log

Created attachment 623381 [details]
messages

In pdb and gdb sessions we found out it hangs in isys.isWirelessDevice. It might be related to Gdk threads locks we use.

I have tried "textinstall" several times and I hadn't encountered this bug.

Created attachment 624104 [details]
Threading code changes used for a test

Also strace reports SIGSEGV signal somewhere (not in Anaconda as it is still running) so we are trying to figure out the relationship between libnm-glib (called from isys), GObject and Gdk locks and Gtk vs. Glib (used to process udev events) mainloop.

The hang happened in Writing network configuration step even when the attached patch was applied (uses Gdk.threads_enter only when necessary and fixes thread initialization).

Created attachment 624106 [details]
strace from anaconda

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

Reproduced in beta TC3 DVD install

For me it hangs when installing onto my T500 but not in virt-manager guests.

With F18 Beta TC3 Live, it now hangs during "Writing network configuration", that means one step further. But it might just be a glitch.

Yep, it always hangs at that spot. Gtk sometimes doesn't redraw the screen fast enough.

Okay, I've found out that the hang happens on the following line:
>    client = nm_client_new();
>(pyanaconda/isys/iface.c:635)
which tries to get new instance of NMClient over DBus. We have also found out that this is probably the only place where we use DBus from a non-main thread. While main thread is running Gtk main loop the separate thread tries to use the same loop for dbus calls which probably causes the hang. It also explains why the issue does not happen in text mode.

We have been doing a revision of Gdk/GLib threading initialization and usage in anaconda. Let's hope it will help.

Having this too with Beta TC3 when "Configuring installed system".

Created attachment 624880 [details]
anaconda.log

Created attachment 624881 [details]
program.log

Created attachment 624888 [details]
storage.log

Discussed at 2012-10-10 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-10/f18beta-blocker-review-3.2012-10-10-16.05.log.txt . Accepted as a blocker per criterion "The installer must be able to complete an installation using the text, graphical and VNC installation interfaces" (even though it turns out the installed system boots, it's certainly true that the install does not 'complete').

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

Not fixed in smoke 7 build netinst.

However, rebooting now during that phase gets you firstboot upon reboot.

if you weren't getting firstboot before, that was https://bugzilla.redhat.com/show_bug.cgi?id=863886 . nothing to do with this bug. this bug is not expected to be fixed yet. it's still set NEW and has no 'fixed in version' set.

Updates image with the patch that seems to resolve this issue is available at:
http://vpodzime.fedorapeople.org/f18_tc3_hang.img

Kamil, could you please test it?

(In reply to comment #43)
> Updates image with the patch that seems to resolve this issue is available
> at:
> http://vpodzime.fedorapeople.org/f18_tc3_hang.img
> 
> Kamil, could you please test it?

With the updates.img I stumbled upon bug 865355.

The updates.img works for me (note: on a machine with no wifi).

(In reply to comment #44)
> (In reply to comment #43)
> > Updates image with the patch that seems to resolve this issue is available
> > at:
> > http://vpodzime.fedorapeople.org/f18_tc3_hang.img
> > 
> > Kamil, could you please test it?
> 
> With the updates.img I stumbled upon bug 865355.
Yeah, but this means it went through the potential hang without any problems.

This seemed to be fixed on smoke7 it just took a really long time.

I did a netinstall of MATE with http://dl.fedoraproject.org/pub/alt/qa/18/20121010_f18b-smoke7/Fedora-18b-smoke7-x86_64-netinst.iso last night. 

(anaconda 18.15) It exited to a black screen after "installing bootloader" screen. There was no screen saying completed and asking for a reboot.

cold boot went to firstboot and sucessful login

anaconda-18.16-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.16-1.fc18

(In reply to comment #48)
> I did a netinstall of MATE with
> http://dl.fedoraproject.org/pub/alt/qa/18/20121010_f18b-smoke7/Fedora-18b-
> smoke7-x86_64-netinst.iso last night. 
> 
> (anaconda 18.15) It exited to a black screen after "installing bootloader"
> screen. There was no screen saying completed and asking for a reboot.
This is the other possible result of this bug. Please try some build with anaconda-18.16-1.fc18 or the updates.img mentioned in commend #43 [1]

[1] http://fedoraproject.org/wiki/Anaconda/Updates#Updates_from_the_Network

updates.img works for me on conventional hardware.

Package anaconda-18.16-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.16-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16018/anaconda-18.16-1.fc18
then log in and leave karma (feedback).

anaconda 18.16 in TC4 lives, DVD and netinstall x86_64 goes to reboot screen and has warning to set root password while installing.

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

This no longer happens in Beta TC4.

anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18

Package anaconda-18.17-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.17-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16295/anaconda-18.17-1.fc18
then log in and leave karma (feedback).

Back to VERIFIED.

anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18

Package anaconda-18.18-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.18-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16402/anaconda-18.18-1.fc18
then log in and leave karma (feedback).

aaaand again.

anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18

Package anaconda-18.19-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.19-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16528/anaconda-18.19-1.fc18
then log in and leave karma (feedback).

This is fixed, anaconda is stable, closing.