Description of problem: Boot F22 Beta TC5 Server DVD x86_64 installer with a (newly created) Intel firmware RAID-0 set attached. Version-Release number of selected component: anaconda-22.20.6-1 The following was filed automatically by anaconda: anaconda 22.20.6-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1593, in handleUdevMDMemberFormat md_info = blockdev.md_examine(device.path) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1877, in handleUdevDeviceFormat self.handleUdevMDMemberFormat(info, device) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 1260, in addUdevDevice self.handleUdevDeviceFormat(info, device) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2177, in _populate self.addUdevDevice(dev) File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 2111, in populate self._populate() File "/usr/lib/python2.7/site-packages/blivet/blivet.py", line 277, in reset self.devicetree.populate(cleanupOnly=cleanupOnly) File "/usr/lib/python2.7/site-packages/blivet/osinstall.py", line 1117, in storageInitialize storage.reset() File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 238, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 112, in wait self.raise_if_error(name) File "/usr/lib64/python2.7/site-packages/pyanaconda/timezone.py", line 75, in time_initialize threadMgr.wait(THREAD_STORAGE) File "/usr/lib64/python2.7/threading.py", line 766, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 238, in run threading.Thread.run(self, *args, **kwargs) Error: g-bd-md-error-quark: Failed to parse mdexamine data (0) Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python2 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-22_B_T5-x86_64 quiet dnf.rpm.log: Mar 27 01:12:13 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.0.0-0.rc4.git0.1.fc22.x86_64 product: Fedora" release: Cannot get release name. type: anaconda version: Fedora
Created attachment 1007052 [details] File: anaconda-tb
Created attachment 1007053 [details] File: anaconda.log
Created attachment 1007054 [details] File: dnf.log
Created attachment 1007055 [details] File: environ
Created attachment 1007056 [details] File: lsblk_output
Created attachment 1007057 [details] File: nmcli_dev_list
Created attachment 1007058 [details] File: os_info
Created attachment 1007059 [details] File: program.log
Created attachment 1007060 [details] File: storage.log
Created attachment 1007061 [details] File: syslog
Created attachment 1007062 [details] File: ifcfg.log
Created attachment 1007063 [details] File: packaging.log
From the libblockdev source: /* we expect at least MD_LEVEL, MD_DEVICES, MD_NAME, MD_UUID, MD_UPDATE_TIME, MD_DEV_UUID, MD_EVENTS */ and it fails if the output has fewer than 7 elements, but my output has only four, MD_METADATA, MD_LEVEL, MD_UUID, and MD_DEVICES. See program.log . Nominating as a Beta blocker: https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria#Hardware_and_firmware_RAID , "The installer must be able to detect and install to hardware or firmware RAID storage devices."
Same result with a RAID-1 set, and also after a reboot.
anaconda-22.20.7-1.fc22, libblockdev-0.8-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/FEDORA-2015-4952/libblockdev-0.8-1.fc22,anaconda-22.20.7-1.fc22
Discussed at 2015-03-30 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2015-03-30/f22-blocker-review.2015-03-30-16.04.log.txt . Accepted as a blocker per criterion cited in #c13.
Package anaconda-22.20.7-1.fc22, libblockdev-0.8-1.fc22: * 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 anaconda-22.20.7-1.fc22 libblockdev-0.8-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-4952/libblockdev-0.8-1.fc22,anaconda-22.20.7-1.fc22 then log in and leave karma (feedback).
I've tested and confirmed the fix for this particular issue, we've now moved on to https://bugzilla.redhat.com/show_bug.cgi?id=1207317 . In fact vpodzime has it to the point where it doesn't crash any more, but does not actually find the RAID set.
anaconda-22.20.7-1.fc22, libblockdev-0.8-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.