Description of problem: Tried to install from kickstart a system with software RAID level 1. Tried numerous incarnations, starting with a ks script that worked up to F17. Version-Release number of selected component: anaconda-18.14 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.1-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.14 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1153, in execute : raise KickstartValueError, formatErrorMsg(self.lineno, msg="Tried to use undefined partition %s in RAID specification" % mem) : File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1082, in execute : r.execute(storage, ksdata, instClass) : File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1559, in doKickstartStorage : ksdata.raid.execute(storage, ksdata, instClass) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 379, in _doExecute : doKickstartStorage(self.storage, self.data, self.instclass) : File "/usr/lib64/python2.7/threading.py", line 504, in run : self.__target(*self.__args, **self.__kwargs) : File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 87, in run : threading.Thread.run(self, *args, **kwargs) :KickstartValueError: The following problem occurred on line 80 of the kickstart file: : :Tried to use undefined partition raid.21 in RAID specification :
Created attachment 624537 [details] File: release
Created attachment 624538 [details] File: product
Created attachment 624539 [details] File: type
Created attachment 624540 [details] File: storage.log
Created attachment 624541 [details] File: version
Created attachment 624542 [details] File: environ
Created attachment 624543 [details] File: anaconda.log
Created attachment 624544 [details] File: syslog
Created attachment 624545 [details] File: hashmarkername
Created attachment 624546 [details] File: packaging.log
Created attachment 624547 [details] File: cmdline_file
Created attachment 624548 [details] File: ks.cfg
Created attachment 624549 [details] File: anaconda-tb
Created attachment 624550 [details] File: program.log
anaconda-18.15-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.15-1.fc18
Package anaconda-18.15-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.15-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15903/anaconda-18.15-1.fc18 then log in and leave karma (feedback).
anaconda-18.16-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.16-1.fc18
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.19-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.
Please, can this bug be re-opened? I am finding exactly this behaviour with anaconda-18.37.11 (that is, anaconda as bundled w/ Fedora 18 on 20130115.) Symptoms are identical to what is described above and (in a non-raid context) here: https://bugzilla.redhat.com/show_bug.cgi?id=853649#c17 - that is, 1. partitions and raid are defined in the kickstart file part /boot --fstype="ext4" blah blah part swap --fstype="swap" blah blah part raid.01 --grow blah blah part raid.02 --grow blah blah raid pv.01 --level=0 --device=md0 --fstype=ext4 raid.01 raid.02 2. anaconda reports "Tried to use undefined partition raid.01 in RAID specification" 3. the 'ksdata' section of anaconda's diagnostic output shows that *raid-relevant* identifiers have disappeared from their corresponding options: part /boot --fstype="ext4" blah blah part --fstype="swap" blah blah part --grow blah blah part --grow blah blah raid --device=0 --fstype="ext4" --level=RAID0 raid.01 raid.02 The 'swap' identified has also disappeared, but apparently this does not generate an error. The kickstart file which generated this error is attached, see below.
Created attachment 696996 [details] kickstart file which generates "undefined partition" error
Created attachment 696998 [details] ks.cfg - fixed bugzilla content-type
Re-opening per John's comments, clearing Fixed-in-Version field.
I cannot reproduce this with anaconda-19.30. If you are able to do so with Fedora 19, please feel free to reopen this bug with your kickstart file and anaconda logs. Thanks.