Description of problem: I tried to reproduce bug 1333131 I used VM with two 15G disks. Firstly I installed system with software raid-1 (custom partitioning - created default lvm layout on empty disks and changed lvm to raid). After installation was done I rebooted back to installer and installed it again. In custom partitioning I erased all the disks and again created default lvm and changed to raid. Installation failed during "setting up the installation environment" phase. Version-Release number of selected component: anaconda-24.13.4-1 The following was filed automatically by anaconda: anaconda 24.13.4-1 exception report Traceback (most recent call first): File "/usr/lib/python3.5/site-packages/blivet/udev.py", line 382, in device_get_md_uuid return util.canonicalize_UUID(info["MD_UUID"]) File "/usr/lib/python3.5/site-packages/blivet/devices/md.py", line 388, in status uuid = udev.device_get_md_uuid(info) File "/usr/lib/python3.5/site-packages/blivet/devices/storage.py", line 491, in destroy log_method_call(self, self.name, status=self.status) File "/usr/lib/python3.5/site-packages/blivet/deviceaction.py", line 363, in execute self.device.destroy() File "/usr/lib/python3.5/site-packages/blivet/actionlist.py", line 280, in process action.execute(callbacks) File "/usr/lib/python3.5/site-packages/blivet/devicetree.py", line 381, in processActions callbacks=callbacks) File "/usr/lib/python3.5/site-packages/blivet/blivet.py", line 164, in doIt self.devicetree.processActions(callbacks=callbacks) File "/usr/lib/python3.5/site-packages/blivet/osinstall.py", line 1096, in turnOnFilesystems storage.doIt(callbacks) File "/usr/lib64/python3.5/site-packages/pyanaconda/install.py", line 195, in doInstall turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg) File "/usr/lib64/python3.5/threading.py", line 862, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.5/site-packages/pyanaconda/threads.py", line 253, in run threading.Thread.run(self, *args, **kwargs) TypeError: 'NoneType' object is not subscriptable Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-24 quiet dnf.rpm.log: May 05 08:52:46 INFO --- logging initialized --- executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.5.2-302.fc24.x86_64 product: Fedora release: Cannot get release name. reproducible: Not sure how to reproduce the problem type: anaconda version: 24
Created attachment 1154135 [details] File: anaconda-tb
Created attachment 1154136 [details] File: anaconda.log
Created attachment 1154137 [details] File: dnf.log
Created attachment 1154138 [details] File: environ
Created attachment 1154139 [details] File: lsblk_output
Created attachment 1154140 [details] File: nmcli_dev_list
Created attachment 1154141 [details] File: os_info
Created attachment 1154142 [details] File: storage.log
Created attachment 1154143 [details] File: syslog
Created attachment 1154144 [details] File: ifcfg.log
Created attachment 1154145 [details] File: packaging.log
Created attachment 1154146 [details] File: program.log
Huh, interesting. Did rebooting and trying again after the crash work, or not?
*** Bug 1366408 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.