Created attachment 477987 [details] anaconda.log Description of problem: On a kvm with F15 installed, try to install F15 again. Delete old partitioning and customize the partioning. After partitioning, An error window pop up(See attached). Traceback in anaconda.log(attached) noted 'No module named iutil' Version-Release number of selected component (if applicable): anaconda 15.19 f15-Alpha-tc1 How reproducible: often Steps to Reproduce: 0. Install F15 or old fedora releases for a kvm. 1. Install F-15 again on this kvm. 2. At partitioning step, choose custom layout to delete old partitions and create new partitions. 3. Error occurred. Actual result: 01:59:08,406 ERR anaconda.stdout: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1309, in setScreen loaded = imp.load_module(moduleName, *found) File "/usr/lib/python2.7/site-packages/pyanaconda/iw/bootloader_main_gui.py", line 24, in <module> import iutil ImportError: No module named iutil
Created attachment 477988 [details] error window
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Wow, it seems related to the partitioning. As long as I create partitions by 'create custom layout', no matter on kvm or bare metal, this error will occur.
Simply reusing an existing partition layout through 'create custom layout' is sufficient to trigger this exception. Anaconda 15.18 did not exhibit this bug.
(In reply to comment #4) > Simply reusing an existing partition layout through 'create custom layout' is > sufficient to trigger this exception. Anaconda 15.18 did not exhibit this bug. Having exactly the same issue: Getting an error message: "An error occured when attempting to load an installer interface component className = MainBootloaderWindow"
Propose it as Alpha blocker since it blocks anyone who tries to partition using 'create custom layout', though it's not included in release criteria[1]. [1] https://fedoraproject.org/wiki/Fedora_15_Alpha_Release_Criteria
*** This bug has been marked as a duplicate of bug 676032 ***