Description of problem: in manual partitioning, i created a 1mb biosboot and a / with no size (aka <null>) in the mount point dialog Version-Release number of selected component: anaconda-18.24 Additional info: libreport version: 2.0.17 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.5-2.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.24 exception report :Traceback (most recent call first): : File "/sbin/anaconda", line 637, in <module> : import updates_disk_hook : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1734, in on_add_clicked : disks=disks) :ImportError: No module named updates_disk_hook
Created attachment 637714 [details] File: anaconda-tb
Created attachment 637715 [details] File: product
Created attachment 637716 [details] File: type
Created attachment 637717 [details] File: ifcfg.log
Created attachment 637718 [details] File: storage.log
Created attachment 637719 [details] File: version
Created attachment 637720 [details] File: environ
Created attachment 637721 [details] File: executable
Created attachment 637722 [details] File: anaconda.log
Created attachment 637723 [details] File: syslog
Created attachment 637724 [details] File: hashmarkername
Created attachment 637725 [details] File: packaging.log
Created attachment 637726 [details] File: cmdline_file
Created attachment 637727 [details] File: release
Created attachment 637728 [details] File: program.log
Are you testing some sort of updates.img or other change? That import is already protected against import errors.
No, just the F18b TC7. No updates of any kind. Default boot parameters. I tried on the same guest with TC7 and TC6 and only TC7 is affected. On previous TCs, the same action crates the partition with the minimum size (1mb). So, by leaving the 'size' field empty in the 'add a mount point' dialog the reported error is triggered with F18b TC7. Previous TC are ok. (I just re-tested with TC6 only).
Just to be sure: $ sha256sum Fedora-18-Beta-TC7-x86_64-DVD.iso 3ad2da960bb6cc8e025cc290a7e4a355531791c4c758339ee0d252976c9a67f9 Fedora-18-Beta-TC7-x86_64-DVD.iso
Oh, I see it now. Wow that's a weird failure case.
anaconda-18.25-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.25-1.fc18
Package anaconda-18.25-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.25-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17691/anaconda-18.25-1.fc18 then log in and leave karma (feedback).
anaconda-18.26-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.26-1.fc18
anaconda-18.27-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.27-1.fc18
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.