libreport version: 2.0.8 cmdline: /usr/bin/python /usr/sbin/anaconda executable: /usr/sbin/anaconda exnFileName: /tmp/anaconda-tb-0OPVaN hashmarkername: anaconda kernel: 3.3.0-0.rc7.git0.3.fc17.i686 other involved packages: product: Fedora reason: IndexError: could not find tree path release: Cannot get release name. time: Mon 19 Mar 2012 03:14:47 AM EDT version: 17-Beta-TC2 anaconda-tb-0OPVaN: Text file, 366142 bytes description: :The following was filed automatically by anaconda: :anaconda 17.13 exception report :Traceback (most recent call first): : File "/usr/lib/python2.7/site-packages/pyanaconda/iw/raid_dialog_gui.py", line 509, in __init__ : selected_level = self.levelcombo.get_model()[level_index][0] : File "/usr/lib/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1676, in editRaidArray : raiddev, isNew) : File "/usr/lib/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1566, in createCB : self.editRaidArray(array, isNew = True) :IndexError: could not find tree path environ: :LANG=en_US.UTF-8 :LC_NUMERIC=C :TERM=linux :BOOT_IMAGE=vmlinuz :XAUTHORITY=/root/.Xauthority :GLADEPATH=/tmp/updates/:/tmp/updates/data/ui/:ui/:/usr/share/anaconda/ui/:/usr/share/python-meh/ :SHLVL=0 :PYTHONPATH=/tmp/updates :PWD=/ :GNOME_DISABLE_CRASH_DIALOG=1 :LIBUSER_CONF=/tmp/libuser.Jzma_m :LVM_SUPPRESS_FD_WARNINGS=1 :initrd=initrd.img :MALLOC_PERTURB_=204 :TZ=America/New_York :GCONF_GLOBAL_LOCKS=1 :HOME=/tmp :PIXMAPPATH=/tmp/updates/pixmaps/:/tmp/updates/:/tmp/product/pixmaps/:/tmp/product/:pixmaps/:/usr/share/anaconda/pixmaps/:/usr/share/pixmaps/:/usr/share/anaconda/:/usr/share/python-meh/:/usr/share/icons/Fedora/48x48/apps/ :PATH=/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin:/sbin:/usr/sbin :MALLOC_CHECK_=2 :DISPLAY=:1
Created attachment 571028 [details] File: anaconda-tb-0OPVaN
anaconda 17.13 failed to testing partitioning On Software RAID, refer to https://fedoraproject.org/wiki/QA:Testcase_Partitioning_On_Software_RAID
anaconda 17.14 still have this problem.
Proposing as Beta blocker. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Discussed at 2012-03-26 QA meeting acting as a blocker review meeting. Agreed that this is a blocker per criterion "The installer must be able to create and install to software, hardware or BIOS RAID-0, RAID-1 or RAID-5 partitions for anything except /boot". -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This is caused by noloader not loading modules before starting Anaconda.
anaconda-17.15-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.15-1.fc17
Package anaconda-17.15-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-17.15-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-4745/anaconda-17.15-1.fc17 then log in and leave karma (feedback).
I was able to do a successful install onto SW Raid (VM w/ 2 virtio disks) with a custom boot.iso built with anaconda-17.15-1.fc17. Not setting to verified because it wasn't an official image but it appears to be fixed.
lorax-17.13-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/lorax-17.13-1.fc17
anaconda-17.16-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/anaconda-17.16-1.fc17
anaconda-17.16-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
Successfully did an install onto SW Raid using F17 beta RC2. Used VM with 2 virtio disks: - 1mb BIOS boot (vda) - 1024 /boot (vda, ext4) - 1025 swap (vdb) - rest of vda, vdb were made into sw raid1
lorax-17.13-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.