Description of problem: Crash on launch. Prior system it's finding is a successful Thin Provisioning installation. The following updated RPMs were applied to F20 Live Beta TC4: anaconda-20.25.1-1 anaconda-widgets "" python-blivet-0.23.1-1 Version-Release number of selected component: anaconda-20.25.1-1.fc20 Additional info: cmdline: /usr/bin/python /usr/bin/anaconda-cleanup anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 dso_list: python-blivet-0.23.1-1.fc20.noarch executable: /usr/bin/anaconda-cleanup kernel: 3.11.4-302.fc20.x86_64 runlevel: N 5 type: Python uid: 0
Created attachment 813168 [details] File: environ
Created attachment 813169 [details] File: os_info
Created attachment 813170 [details] anaconda.log
Created attachment 813171 [details] storage.log
Created attachment 813172 [details] program.log
Created attachment 813173 [details] journalctl -b
*** Bug 1020117 has been marked as a duplicate of this bug. ***
Created attachment 813176 [details] backtrace for reproduced crash
See if this updates image helps: http://dlehman.fedorapeople.org/updates/updates-1020111.0.img Thanks.
DVD ISO beta TC5 without this updates img applied, does not crash. So this bug 102011 or bug 101300 appears squashed. Live desktop beta TC4 with the three rpm updates, and this updates img, still crashes. Maybe it's better to just axe TC4 and this update img, and move to live desktop TC5.
c10 correction: bug 1020111 or bug 103800 Fedora-Live-Desktop-x86_64-20-Beta-TC5.iso crashes with or without updates-1020111.0.img.
Created attachment 813524 [details] c11 anaconda.log update.img is present ll /tmp 3499 Oct 17 15:22 updates.img
Created attachment 813526 [details] c11 backtrace
(In reply to Chris Murphy from comment #12) > Created attachment 813524 [details] > c11 anaconda.log > > update.img is present > ll /tmp > 3499 Oct 17 15:22 updates.img How are you applying the updates image? On the boot/kernel cmdline? I am asking because the patch in the updates image fixes the lvm leaked fd messages completely for me. I'm not even seeing a crash with Fedora-Live-Desktop-x86_64-20-Beta-TC5.iso without the updates/patch.
It's applied on kernel command line from the isolinux boot menu. No crash for DVD ISO, but I get a crash with or without update applied with live desktop; anaconda UI still comes up but right before that I have an abrt crash notification.
So far the easiest way to always reproduce this is: 1. qemu/kvm using qcow2 for disk backing, boot F20 beta TC5 DVD ISO, guided partitioning scheme=LVM Thin Provisioning, minimal package set, install. 2. Switch to F20 beta TC5 live desktop ISO, boot, at Welcome to Fedora splash choose Install to Hard Drive. Result: At the bottom of the screen an abrt message appears: "A Problem Has Occurred A problem in the anaconda-20.25.1-1..." And behind it I see anaconda's select language page. I can get to the hub just fine. If I launch ABRT, one item is listed in the System tab which is how I originally filed this bug: anaconda crashed devicetree.py:1294:addLV:ValueError: 'File desc... Occurs with or without the c9 updates.img on isolinux boot line.
Please run this command on the live system with updates applied: grep -n close_fds /usr/lib/python2.7/site-packages/blivet/util.py And report the output here. Thanks.
There is no output from that command before or after launching anaconda (updates.img doesn't appear in /tmp until after launching anaconda).
If I go into /tmp/updates/blivet and run the command: [liveuser@localhost blivet]$ grep -n close_fds util.py 39: close_fds=True, So I think the updates haven't been downloaded by the time the bug is hit. If I quit anaconda, and relaunch, there is no abrt message a 2nd go around. So I think this is fixed, but I don't understand the updates mechanism very well.
Discussed at 2013-10-23 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-23/f20-blocker-review.2013-10-23-16.00.log.txt . Accepted as a blocker as a conditional violation of Alpha criterion "The installer must run when launched normally from the release-blocking images." - https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria#Installer_must_run - in the case of a system with a pre-existing, anaconda-created LVM thinp layout.
anaconda-20.25.4-1.fc20, pykickstart-1.99.44-1.fc20, python-blivet-0.23.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/pykickstart-1.99.44-1.fc20,python-blivet-0.23.2-1.fc20,anaconda-20.25.4-1.fc20
Package anaconda-20.25.4-1.fc20, pykickstart-1.99.44-1.fc20, python-blivet-0.23.2-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-20.25.4-1.fc20 pykickstart-1.99.44-1.fc20 python-blivet-0.23.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20033/pykickstart-1.99.44-1.fc20,python-blivet-0.23.2-1.fc20,anaconda-20.25.4-1.fc20 then log in and leave karma (feedback).
Not reproducible with Fedora-20-Beta-TC6-x86_64-DVD.iso or Fedora-Live-Desktop-x86_64-20-Beta-TC6.iso which has: anaconda-20.25.4-1.fc20 pykickstart-1.99.44-1.fc20 python-blivet-0.23.2-1.fc20
Seems fixed in Fedora 20 Beta TC6.
anaconda-20.25.4-1.fc20, pykickstart-1.99.44-1.fc20, python-blivet-0.23.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.