Bug 1333301

Summary: TypeError: 'NoneType' object is not subscriptable
Product: [Fedora] Fedora Reporter: Petr Schindler <pschindl>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, kurt, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:34af39eef1b61a7a4bae35b594bb372eb0f97dd3e2308affa372823013102d20;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 14:24:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: dnf.log
none
File: environ
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: storage.log
none
File: syslog
none
File: ifcfg.log
none
File: packaging.log
none
File: program.log none

Description Petr Schindler 2016-05-05 09:00:15 UTC 
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
Comment 1 Petr Schindler 2016-05-05 09:01:31 UTC 
Created attachment 1154135 [details]
File: anaconda-tb
Comment 2 Petr Schindler 2016-05-05 09:01:40 UTC 
Created attachment 1154136 [details]
File: anaconda.log
Comment 3 Petr Schindler 2016-05-05 09:01:41 UTC 
Created attachment 1154137 [details]
File: dnf.log
Comment 4 Petr Schindler 2016-05-05 09:01:43 UTC 
Created attachment 1154138 [details]
File: environ
Comment 5 Petr Schindler 2016-05-05 09:01:44 UTC 
Created attachment 1154139 [details]
File: lsblk_output
Comment 6 Petr Schindler 2016-05-05 09:01:46 UTC 
Created attachment 1154140 [details]
File: nmcli_dev_list
Comment 7 Petr Schindler 2016-05-05 09:01:47 UTC 
Created attachment 1154141 [details]
File: os_info
Comment 8 Petr Schindler 2016-05-05 09:02:22 UTC 
Created attachment 1154142 [details]
File: storage.log
Comment 9 Petr Schindler 2016-05-05 09:02:27 UTC 
Created attachment 1154143 [details]
File: syslog
Comment 10 Petr Schindler 2016-05-05 09:02:28 UTC 
Created attachment 1154144 [details]
File: ifcfg.log
Comment 11 Petr Schindler 2016-05-05 09:02:30 UTC 
Created attachment 1154145 [details]
File: packaging.log
Comment 12 Petr Schindler 2016-05-05 09:02:33 UTC 
Created attachment 1154146 [details]
File: program.log
Comment 13 Adam Williamson 2016-05-05 14:53:22 UTC 
Huh, interesting. Did rebooting and trying again after the crash work, or not?
Comment 14 Kurt Keller 2016-08-11 22:31:11 UTC 
*** Bug 1366408 has been marked as a duplicate of this bug. ***
Comment 15 Fedora End Of Life 2017-07-25 20:40:38 UTC 
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.
Comment 16 Fedora End Of Life 2017-08-08 14:24:55 UTC 
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.