Description of problem: I created a GPT table partition in my blank disk using the text console, then switch back to the GUI and see a unknown partition, when I tried to delete it, it crashed. Version-Release number of selected component: anaconda-20.25.6-1 The following was filed automatically by anaconda: anaconda 20.25.6-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 302, in _removeDevice if dev.partedPartition.type == parted.PARTITION_EXTENDED and \ File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 351, in registerAction self._removeDevice(action.device) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1218, in destroyDevice self.devicetree.registerAction(action) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2077, in _destroy_device self.__storage.destroyDevice(device) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2201, in on_remove_clicked self._destroy_device(device) AttributeError: 'NoneType' object has no attribute 'type' Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Beta\x20x86_64 quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.6-301.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 20-Beta
Created attachment 821498 [details] File: anaconda-tb
Created attachment 821499 [details] File: anaconda.log
Created attachment 821500 [details] File: environ
Created attachment 821501 [details] File: lsblk_output
Created attachment 821502 [details] File: nmcli_dev_list
Created attachment 821503 [details] File: os_info
Created attachment 821504 [details] File: program.log
Created attachment 821505 [details] File: storage.log
Created attachment 821506 [details] File: syslog
Created attachment 821507 [details] File: ifcfg.log
Created attachment 821508 [details] File: packaging.log
Did you use the 'Reload storage configuration from disk' button next to the minus button below the list mountpoints/systems after doing that change in console?
(In reply to Vratislav Podzimek from comment #12) > Did you use the 'Reload storage configuration from disk' button next to the > minus button below the list mountpoints/systems after doing that change in > console? I think I didn't use that button.
Well, then this won't be fixed, because Anaconda cannot/won't automatically find out something has changed on the disks. That's the purpose of the (maybe a bit hidden) button. I think the Installation Guide should stress that out.