Description of problem: Trying to remove a LUKS partition in the manual partition handling screen. Highlighted the partition, which showed up in the "Fedora Linux 24" section, then pressed the "-" button at the bottom. Version-Release number of selected component: anaconda-24.12-1 The following was filed automatically by anaconda: anaconda 24.12-1 exception report Traceback (most recent call first): File "/usr/lib/python3.5/site-packages/blivet/devicetree.py", line 226, in _removeDevice raise ValueError("Cannot remove non-leaf device '%s'" % dev.name) File "/usr/lib/python3.5/site-packages/blivet/devicetree.py", line 317, in registerAction self._removeDevice(action.device) File "/usr/lib/python3.5/site-packages/blivet/blivet.py", line 1095, in destroyDevice self.devicetree.registerAction(action) File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1857, in _destroy_device self._storage_playground.destroyDevice(device) File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 137, in decorated return func(*args, **kwargs) File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2011, in on_remove_clicked self._destroy_device(device) ValueError: Cannot remove non-leaf device 'nvme0n1p5' Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=Fedora-rawhide-x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.5.0-0.rc3.git3.1.fc24.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: rawhide
Created attachment 1128826 [details] File: anaconda-tb
Created attachment 1128827 [details] File: anaconda.log
Created attachment 1128828 [details] File: dnf.log
Created attachment 1128829 [details] File: dnf.rpm.log
Created attachment 1128830 [details] File: environ
Created attachment 1128831 [details] File: lsblk_output
Created attachment 1128832 [details] File: nmcli_dev_list
Created attachment 1128833 [details] File: os_info
Created attachment 1128834 [details] File: storage.log
Created attachment 1128835 [details] File: syslog
Created attachment 1128836 [details] File: ifcfg.log
Created attachment 1128837 [details] File: packaging.log
Created attachment 1128838 [details] File: program.log
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
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.