The following was filed automatically by anaconda:
anaconda 13.38 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/devices.py", line 321, in createParents
raise DeviceError("parent device does not exist", self.name)
File "/usr/lib/anaconda/storage/devices.py", line 2804, in create
File "/usr/lib/anaconda/storage/deviceaction.py", line 203, in execute
File "/usr/lib/anaconda/storage/devicetree.py", line 678, in processActions
File "/usr/lib/anaconda/storage/__init__.py", line 283, in doIt
File "/usr/lib/anaconda/packages.py", line 109, in turnOnFilesystems
File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
File "/usr/lib/anaconda/gui.py", line 1313, in nextClicked
DeviceError: ('parent device does not exist', 'md1')
Created attachment 409640 [details]
Attached traceback automatically from anaconda.
Looking at the attached logs. You were starting with a standard autopartitioned install using 2 entire disks. Then did custom partitioning, and removed all pre-existing partitions. Then created 2 mdraid partitions on each disk, 1 to hold a mdraid mirror containing /boot, and another for an mdraid set for /, correct ?
If you look at the action pruning part of the log you'll see that for some reason the device and format create actions for sda2 gets pruned, so when we try to create the mdraid set using sda2 and sdb2, we get this backtrace. moving this over to dlehman.
This should be fixed in anaconda-13.39-1 by commit f420bf4f8 (the "Also..." part).
Jesse, can you please re-test ASAP? Thanks. TC1 has 13.39.
Fedora Bugzappers volunteer triage team