Created attachment 1021165 [details]
anaconda log file
Description of problem:
Instalation of Fedora 22 Beta Server failed.
Version-Release number of selected component (if applicable):
15:30:39,442 CRIT anaconda: Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 244, in run
threading.Thread.run(self, *args, **kwargs)
File "/usr/lib64/python2.7/threading.py", line 766, in run
File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 1117, in storageInitialize
File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 277, in reset
File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2128, in populate
File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2194, in _populate
File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1262, in addUdevDevice
File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1894, in handleUdevDeviceFormat
File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1595, in handleUdevMDMemberFormat
md_info = blockdev.md_examine(device.path)
Created attachment 1021166 [details]
Created attachment 1021167 [details]
Created attachment 1021168 [details]
another anaconda log
The problem is that the 'mdadm --examine --brief' doesn't provide the 'metadata=X' key-value in some cases and libblockdev expected that. The easy fix is to not require that key-value. I checked that blivet is ready to get the results with no metadata version set.
Proposed as a Freeze Exception for 22-final by Fedora user vpodzime using the blocker tracking app because:
Could with high probability happen on some FW RAID installations.
As I recall, the set of fields output by mdadm examine depends on the metadata version of the md superblock. It would certainly be nicer if it were consistent instead.
This partially depends on whether you are talking about --examine or --examine --brief. The latter is specifically intended to be a suitable ARRAY line in an mdadm.conf file, so the information displayed is only what's needed by mdadm to reliably, uniquely identify the array and preserve its current name. I suspect it only outputs a metadata version for 0.90 arrays, and then only because that's a deprecated metadata version, but I could be wrong on the reason for it. Neil might be amenable to making the metadata version output constant.
Discussed at the 2015-05-11 blocker review meeting. Voted as AcceptedFreezeException.
AGREED: 1217900 - AcceptedFreezeException - any reasonable fix to a crasher in sensible anaconda usage is a good thing to get in (adamw, 18:09:12)
We're now past the final freeze - it'd be good to get a build with this fix (and the other accepted FE in libblockdev, which is in POST state) ASAP, so we have longer to test. Thanks!
libblockdev-0.13-1.fc22 has been submitted as an update for Fedora 22.
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libblockdev-0.13-1.fc22'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libblockdev-0.13-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.