Created attachment 1570612 [details]
File: anaconda-tb

Created attachment 1570613 [details]
File: anaconda.log

Created attachment 1570614 [details]
File: dbus.log

Created attachment 1570615 [details]
File: dnf.librepo.log

Created attachment 1570616 [details]
File: environ

Created attachment 1570617 [details]
File: hawkey.log

Created attachment 1570618 [details]
File: ks.cfg

Created attachment 1570619 [details]
File: lorax-packages.log

Created attachment 1570620 [details]
File: lsblk_output

Created attachment 1570621 [details]
File: nmcli_dev_list

Created attachment 1570622 [details]
File: os_info

Created attachment 1570624 [details]
File: program.log

Created attachment 1570627 [details]
File: storage.log

Created attachment 1570629 [details]
File: syslog

Created attachment 1570630 [details]
File: packaging.log

Similar problem has been detected:

F30/x86_64 installation with kickstart, installation sources are on locally mirrored NFS accessed repos.
Anaconda show initial GUI screen. After clicking on "Installation Destination" (this item has warning label
"Kickstart insufficient" - which is true), installer crashes.
System contains 2x NVMe + 4x rotational disks.

I don't know what caused this problem, but is it possible to say, that is anaconda big problem and crash due to
disks layout is allmost normal behavior.

addons:         com_redhat_kdump
blivet-gui-utils.log: 
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-30 net.ifnames=0 inst.ks=http://adm.hanzlici.cz/ks/30/saz64-ks.cfg
hashmarkername: anaconda
kernel:         5.0.9-301.fc30.x86_64
package:        anaconda-30.25.6
product:        Fedora
reason:         TypeError: 'NoneType' object is not subscriptable
release:        Fedora release 30 (Thirty)
version:        30

From the traceback:

anaconda 30.25.6 exception report
Traceback (most recent call first):
  File "/usr/lib64/python3.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 687, in _add_disk_overview
    description = desc[0:6] + "..." + desc[-8:]
  File "/usr/lib64/python3.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 628, in refresh
    self._add_disk_overview(obj, self._specialized_disks_box)
  File "/usr/lib64/python3.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 420, in _on_spoke_clicked
    spoke.refresh()
TypeError: 'NoneType' object is not subscriptable

Local variables in innermost frame:
self: StorageSpoke
disk: existing 476.94 GiB dm-multipath mpatha (291) with existing gpt disklabel
box: <Gtk.Box object at 0x7f5f2f614bd0 (GtkBox at 0x5606afd342e0)>
kind: drive-harddisk
popup_info: None
desc: None

and the Anaconda code:
https://github.com/rhinstaller/anaconda/blob/5c492721676257d239ebc38fbacafc96f944f856/pyanaconda/ui/gui/spokes/storage.py#L686

I wonder why the disk does have wwn attribute with None value.

We should be robust enough to cope with None value better, but I'd like to ask our storage library people if there is some other issue that deserves attention. I was not able to see anything in the logs, reassigning for investigating.

Anaconda PR with patch preventing crash when using the None value in GUI:
https://github.com/rhinstaller/anaconda/pull/2263

(In reply to Radek Vykydal from comment #18)
> Anaconda PR with patch preventing crash when using the None value in GUI:
> https://github.com/rhinstaller/anaconda/pull/2263

Will be included in anaconda-32.19-1.

*** Bug 1807486 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.